CVE-2023-48708: Insertion of Sensitive Information into Log
Impact If successful login attempts are recorded, the raw tokens are stored in the log table. If a malicious person somehow views the data in the log table, he or she can obtain a raw token, which can then be used to send a request with that user's authority.
When you (1) use the following authentiactors, - AccessTokens (tokens) - JWT (jwt) - HmacSha256 (hmac)
and you (2) log successful login attempts, the raw tokens are stored.
Patches Upgrade to Shield v1.0.0-beta.8 or later.
Workarounds Disable logging for successful login attempts by the configuration files.
- AccessTokens or HmacSha256 - Set Config\AuthToken::$recordLoginAttempt to Auth::RECORDLOGINATTEMPTFAILURE or Auth::RECORDLOGINATTEMPTNONE - JWT - Set Config\AuthJWT::$recordLoginAttempt to Auth::RECORDLOGINATTEMPTFAILURE or Auth::RECORDLOGINATTEMPTNONE
References - https://codeigniter4.github.io/shield/gettingstarted/authenticators/
For more information If you have any questions or comments about this advisory: Open an issue or discussion in codeigniter4/shield Email us at security@codeigniter.com
Other sources
CodeIgniter Shield is an authentication and authorization provider for CodeIgniter 4. In affected versions successful login attempts are recorded with the raw tokens stored in the log table. If a malicious person somehow views the data in the log table they can obtain a raw token which can then be used to send a request with that user's authority. This issue has been addressed in version 1.0.0-beta.8. Users are advised to upgrade. Users unable to upgrade should disable logging for successful login attempts by the configuration files.
Insertion of Sensitive Information into Log
— Packagist
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/codeigniter4/shieldto a version that resolves this vulnerability.Fixed in 1.0.0-beta.8 - Upgrade
Upgrade
codeigniter4/shieldto a version that resolves this vulnerability.Fixed in 1.0.0-beta.8 - Configuration
Disable logging of successful login attempts by setting Config\AuthJWT::$recordLoginAttempt and Config\AuthToken::$recordLoginAttempt to Auth::RECORD_LOGIN_ATTEMPT_FAILURE or Auth::RECORD_LOGIN_ATTEMPT_NONE in the configuration files.
CodeIgniter Shield Config\AuthJWT::$recordLoginAttempt and Config\AuthToken::$recordLoginAttempt = Auth::RECORD_LOGIN_ATTEMPT_FAILURE or Auth::RECORD_LOGIN_ATTEMPT_NONE
Event History
Frequently Asked Questions
What is the impact of CVE-2023-48708?
If successful login attempts are recorded, the raw tokens are stored in the log table and can be obtained by a malicious person, allowing them to send requests with the user's authority.
How can a malicious person obtain raw tokens from the log table?
If a malicious person somehow views the data in the log table, they can obtain a raw token.
What can a malicious person do with a raw token obtained from the log table?
A malicious person can use a raw token to send requests with the authority of the user associated with that token.
What version of codeigniter4/shield is affected by CVE-2023-48708?
The vulnerability affects codeigniter4/shield version 1.0.0-beta.8 exclusively.
Where can I find more information about codeigniter4/shield and fixing this vulnerability?
You can find more information about codeigniter4/shield and how to fix this vulnerability in the references provided: https://github.com/codeigniter4/shield/security/advisories/GHSA-j72f-h752-mx4w, https://github.com/codeigniter4/shield/commit/7e84c3fb3411294f70890819bfe51781bb9dc8e4, https://codeigniter4.github.io/shield/getting_started/authenticators/