CVE-2023-48708: Insertion of Sensitive Information into Log

Published Nov 23, 2023
·
Updated

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

9 affected componentsFixes available
composer/codeigniter4/shield<1.0.0-beta.8
1.0.0-beta.8
CodeIgniter shield=1.0.0-beta
CodeIgniter shield=1.0.0-beta2
CodeIgniter shield=1.0.0-beta3
CodeIgniter shield=1.0.0-beta4
CodeIgniter shield=1.0.0-beta5
CodeIgniter shield=1.0.0-beta6
CodeIgniter shield=1.0.0-beta7
composer/codeigniter4/shield<1.0.0-beta.8
1.0.0-beta.8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/codeigniter4/shield to a version that resolves this vulnerability.

    Fixed in 1.0.0-beta.8
  2. Upgrade

    Upgrade codeigniter4/shield to a version that resolves this vulnerability.

    Fixed in 1.0.0-beta.8
  3. 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

Nov 23, 2023
Advisory Published
12:28 AM
Data Sourced
via GitHub·12:28 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Packagist·12:28 AM
DescriptionSeverityAffected Software
Nov 24, 2023
CVE Published
via MITRE·05:16 PM
Data Sourced
via MITRE·05:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

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.

2

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.

3

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.

4

What version of codeigniter4/shield is affected by CVE-2023-48708?

The vulnerability affects codeigniter4/shield version 1.0.0-beta.8 exclusively.

5

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/

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203