CVE-2023-45184
Published: 14 December 2023
Summary
CVE-2023-45184 is a medium-severity Insecure Storage of Sensitive Information (CWE-922) vulnerability in Ibm I Access Client Solutions. Its CVSS base score is 6.2 (Medium).
Operationally, ranked in the top 7.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
IBM i Access Client Solutions versions 1.1.2 through 1.1.4 and 1.1.4.3 through 1.1.9.3 contain a vulnerability that could allow an attacker to obtain a decryption key due to improper authority checks. The flaw is tracked as CVE-2023-45184 with an associated IBM X-Force ID of 268270, carries a CVSS 3.1 base score of 6.2, and is categorized under CWE-922.
A local attacker with no privileges and no user interaction required can exploit the issue over the local attack vector to achieve high confidentiality impact by retrieving the decryption key.
IBM has published advisories addressing the vulnerability at https://www.ibm.com/support/pages/node/7091942 and the corresponding X-Force entry at https://exchange.xforce.ibmcloud.com/vulnerabilities/268270. The EPSS score remains flat at a peak and current value of 0.0775 with no material rise observed after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-49491
Vulnerability details
IBM i Access Client Solutions 1.1.2 through 1.1.4 and 1.1.4.3 through 1.1.9.3 could allow an attacker to obtain a decryption key due to improper authority checks. IBM X-Force ID: 268270.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Tracking information locations and access supports secure storage practices instead of insecure ones.
Establishing an alternate site with equivalent protections directly mitigates insecure storage of sensitive backup information.
Requiring protection of backup information directly addresses insecure storage of sensitive data in backups.
Policy explicitly addresses insecure storage of CUI on external systems, requiring compliant handling and protections.
Proper categorization drives selection of storage controls that keep sensitive information from being stored insecurely.
The control explicitly requires secure storage mechanisms for sensitive information, closing the insecure-storage weakness class.
Storing information as fragments on distinct components is an architectural control that avoids insecure single-location storage of the complete sensitive data set.
OPSEC requirements improve handling and storage practices for sensitive supply-chain information.