CVE-2023-22878
Ibm Infosphere Information Server 11.7
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-22878 is a medium-severity Cleartext Storage of Sensitive Information (CWE-312) vulnerability in Ibm Infosphere Information Server. Its CVSS base score is 6.2 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Proc Filesystem (T1003.007); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-26988
Vulnerability Data
IBM InfoSphere Information Server 11.7 stores user credentials in plain clear text which can be read by a local user. IBM X-Force ID: 244373.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 3 OS baselines
V14.2.8
Likely Mitigating Controls
Our mappings. 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.
Training on secure data handling discourages cleartext storage of sensitive information.
Data action mapping can detect storage actions that leave sensitive information in cleartext.
Configuration policies can mandate secure storage methods to avoid cleartext storage of sensitive information.
Policy requires protection measures such as encryption for sensitive data stored on media, preventing cleartext exposure.
Key-management policy requires protected storage of key material, preventing cleartext storage of sensitive cryptographic keys.
Requiring confidentiality protection for information at rest eliminates cleartext storage of sensitive data on persistent media.
Reduces cleartext storage of sensitive data when OPSEC identifies and mandates protection of key information artifacts.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Encryption and cryptographic controls for data-at-rest directly prevent cleartext storage of sensitive information.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
created from the owner's anchor; an owner grade is a row and does not wait for an instrument (Mythos 2026-09-29T15:58Z).
Code review and static analysis can identify cleartext-storage patterns while runtime and penetration tests can expose accessible plaintext stores, leaving a bounded remainder in opaque services, unexercised paths, and context-dependent sensitive-data flows.
A.8.3 restricts who can reach the storage location, which blocks exploitation of the cleartext by unauthorized actors; the remainder is bounded and nameable — insider threats with legitimate access, compromised credentials, and access-control misconfigurations — where the cleartext is immediately readable once the access boundary is crossed.
A.5.15 mandates a topic-specific access control policy and rules for authorizing access to information, but it does not itself encrypt stored data or prevent cleartext storage from being exploited once it exists.
A.5.17 mandates that passwords be stored in protected form (encrypted/hashed per approved cryptographic techniques) and transmitted securely, which removes the cleartext-storage weakness for authentication information specifically; however, CWE-312 covers all sensitive information (PHI, financial data, configuration secrets, etc.), and A.5.17's scope is limited to authentication information, so it addresses only a portion of the weakness class.
A.7.10(d) requires cryptographic protection of information on removable storage media when confidentiality matters, so applying the clause to a system that previously stored sensitive data in cleartext on such media removes that subset of CWE-312 instances; the remainder is the broader class of cleartext storage in databases, cookies, memory, config files, and other non-storage-media resources that A.7.10 does not reach.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
Oracle Linux 8 (1 rule)
- V-248525 All OL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at-rest protection. blocks CWE-312
Oracle Linux 9 (1 rule)
- V-271756 OL 9 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. blocks CWE-312
RHEL 8 (1 rule)
- V-230224 All RHEL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. blocks CWE-312