CVE-2023-48707: Cleartext Storage of Sensitive Information in HMAC SHA256 Authentication

Published Nov 23, 2023
·
Updated

Impact secretKey, an important key for HMAC SHA256 authentication, was stored in the database in raw form.

If a malicious person somehow had access to the data in the database, they could use the key and secretKey for HMAC SHA256 authentication to send requests impersonating that person.

Patches Upgrade to Shield v1.0.0-beta.8 or later.

After upgrading, all existing secret keys must be encrypted. See https://github.com/codeigniter4/shield/blob/develop/UPGRADING.md for details.

Workarounds None.

References - https://codeigniter4.github.io/shield/references/authentication/hmac/

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

Cleartext Storage of Sensitive Information in HMAC SHA256 Authentication

— Packagist

CodeIgniter Shield is an authentication and authorization provider for CodeIgniter 4. The secretKey value is an important key for HMAC SHA256 authentication and in affected versions was stored in the database in cleartext form. If a malicious person somehow had access to the data in the database, they could use the key and secretKey for HMAC SHA256 authentication to send requests impersonating that corresponding user. This issue has been addressed in version 1.0.0-beta.8. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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. Operational

    After upgrading, encrypt all existing secretKey values.

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:23 PM
Data Sourced
via MITRE·05:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2023-48707?

The severity of CVE-2023-48707 is medium.

2

How does CVE-2023-48707 impact codeigniter4/shield?

CVE-2023-48707 allows a malicious person with access to the database to impersonate others using the secretKey for HMAC SHA256 authentication.

3

How do I fix CVE-2023-48707?

To fix CVE-2023-48707, update codeigniter4/shield to version 1.0.0-beta.8.

4

Where can I find more information about CVE-2023-48707?

You can find more information about CVE-2023-48707 at the following references: [GitHub Advisory](https://github.com/codeigniter4/shield/security/advisories/GHSA-v427-c49j-8w6x), [GitHub Commit](https://github.com/codeigniter4/shield/commit/f77c6ae20275ac1245330a2b9a523bf7e6f6202f), [NVD](https://nvd.nist.gov/vuln/detail/CVE-2023-48707).

5

What is the CWE ID for CVE-2023-48707?

The CWE ID for CVE-2023-48707 is 312.

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