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::$recordLoginAttempttoAuth::RECORD_LOGIN_ATTEMPT_FAILUREorAuth::RECORD_LOGIN_ATTEMPT_NONE
- Set
- JWT
- Set
Config\AuthJWT::$recordLoginAttempttoAuth::RECORD_LOGIN_ATTEMPT_FAILUREorAuth::RECORD_LOGIN_ATTEMPT_NONE
- Set
References
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
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | codeigniter4/shield | < 1.0.0-beta.8 | 1.0.0-beta.8 |
References
- https://github.com/codeigniter4/shield/security/advisories/GHSA-j72f-h752-mx4w
- https://nvd.nist.gov/vuln/detail/CVE-2023-48708
- https://github.com/codeigniter4/shield/commit/7e84c3fb3411294f70890819bfe51781bb9dc8e4
- https://codeigniter4.github.io/shield/getting_started/authenticators
- https://github.com/codeigniter4/shield
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:N- Weakness (CWE)
CWE-532- Platform
- Composer
- Package
codeigniter4/shield- Disclosed
- 23.11.2023
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-j72f-h752-mx4w - CC BY 4.0
Vulnerability history: codeigniter4/shield
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 4
- First → latest
- 08.2022 11.2023
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Medium 4
Disclosures per year
- 2022: 1
- 2023: 3
- 2024: 0
- 2025: 0
- 2026: 0
-
Insertion of Sensitive Information into Log this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.