Skip to content

Insertion of Sensitive Information into Log

Moderate severity GitHub Reviewed Published Nov 23, 2023 in codeigniter4/shield • Updated Nov 27, 2023

Package

composer codeigniter4/shield (Composer)

Affected versions

< 1.0.0-beta.8

Patched versions

1.0.0-beta.8

Description

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,

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::RECORD_LOGIN_ATTEMPT_FAILURE or Auth::RECORD_LOGIN_ATTEMPT_NONE
  • JWT
    • Set Config\AuthJWT::$recordLoginAttempt to Auth::RECORD_LOGIN_ATTEMPT_FAILURE or Auth::RECORD_LOGIN_ATTEMPT_NONE

References

For more information

If you have any questions or comments about this advisory:

References

@kenjis kenjis published to codeigniter4/shield Nov 23, 2023
Published to the GitHub Advisory Database Nov 23, 2023
Reviewed Nov 23, 2023
Published by the National Vulnerability Database Nov 24, 2023
Last updated Nov 27, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:N

EPSS score

0.128%
(48th percentile)

Weaknesses

CVE ID

CVE-2023-48708

GHSA ID

GHSA-j72f-h752-mx4w

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.