CVE-2023-33837
Ibm Security Verify Governance 10.0
Raw vector
CVSS:3.1/AV:L/AC:H/PR:H/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-33837 is a medium-severity Cleartext Transmission of Sensitive Information (CWE-319) vulnerability in Ibm Security Verify Governance. Its CVSS base score is 4.1 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 21th 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-37987
Vulnerability Data
IBM Security Verify Governance 10.0 does not encrypt sensitive or critical information before storage or transmission. IBM X-Force ID: 256020.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
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.
Privacy and security training stresses encryption of sensitive data, reducing missing encryption weaknesses.
Exchange agreements must document security requirements, which would include encryption to protect sensitive data in transit.
The map highlights data actions that involve sensitive data, enabling identification of missing encryption requirements.
Settings can require encryption of sensitive data, preventing missing encryption weaknesses.
Requires encryption and similar controls for CUI processed or stored externally, preventing missing encryption of sensitive data.
Privacy and security requirements placed on external providers, together with monitoring, tangibly reduce missing encryption of sensitive data processed or stored by those services.
Mandates encryption for specified data uses, directly preventing missing encryption of sensitive information.
Policy addresses secure transport and handling of media to avoid cleartext transmission of sensitive information.
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 of data-in-transit directly prevents cleartext transmission while the control also addresses integrity and availability.
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.
A.8.24's guidance item (c) explicitly names cryptography for protection of information 'transmitted over networks', so a well-implemented clause mandates encryption of data in transit; the cleartext transmission weakness stops being present, parallel to the owner's A.8.24 removes CWE-311/CWE-312 = full rulings on the same clause text.
A.8.21 mandates identifying/implementing network service security features (explicitly including encryption and connection controls), formulating rules that cover authentication/authorization/monitoring/VPNs, and ensuring providers do the same; this stops cleartext transmission from being exploitable in the large majority of network channels, with a bounded remainder (e.g. internal non-networked flows or unaddressed legacy protocols).
Mandating cryptographic protection and stronger authentication on public networks stops the transmission of plaintext sensitive information.
A.5.17 mandates secure transmission of authentication information, removing cleartext transmission of that specific sensitive data, but does not address other sensitive information transmitted in cleartext, so it removes only a subset of CWE-319 instances.
Training helps where cleartext transmission is a developer or administrator choice (HTTP vs HTTPS, enabling secure transfer, not sending credentials in email) — the same logic that graded A.6.3 vs CWE-1428 at `mostly` — but CWE-319 is broader than CWE-1428 and includes hardware debug channels (JTAG), OT/ICS protocol choices baked into vendor products, and legacy systems where the protocol decision is not a conscious act by someone training can reach, leaving a nameable remainder that puts this below `mostly`.
A.6.7 mandates communications security requirements for remote access (items d, h, k) and the provision of suitable communication equipment with methods for securing remote access, which blocks cleartext transmission during remote working; however, CWE-319 applies to all communication channels — internal networks, server-to-server, hardware/JTAG, application-layer — and A.6.7's scope is limited to remote working, leaving the bulk of cleartext-transmission instances outside its reach.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-311, a class-level weakness. Rules are authored against its narrower children: CWE-312.