CVE-2023-31004
Ibm Security Verify Access 10.0.0.0 – 10.0.6.1
Raw vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-31004 is a high-severity Channel Accessible by Non-Endpoint (CWE-300) vulnerability in Ibm Security Verify Access. Its CVSS base score is 8.3 (High).
Operationally, ranked in the top 38% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-3 (Device Identification and Authentication) and SC-11 (Trusted Path) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-35342
Vulnerability Data
IBM Security Access Manager Container (IBM Security Verify Access Appliance 10.0.0.0 through 10.0.6.1 and IBM Security Verify Access Docker 10.0.0.0 through 10.0.6.1) could allow a remote attacker to gain access to the underlying system using man in the middle techniques.…
more
IBM X-Force ID: 254765.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
IA-3 mandates device identification and authentication prior to establishing communications, addressing the non-endpoint actor risk.
SC-23 enforces session authenticity protections that verify both endpoints and prevent channel manipulation by outsiders.
SC-11 provides an isolated trusted path that cryptographically or physically assures the identities of the two endpoints.
SC-8 directly requires cryptographic or equivalent mechanisms to protect the integrity (and confidentiality) of transmitted data, stopping non-endpoint interference.
AC-17 requires documented usage restrictions and secure configuration for remote access channels, reducing exposure to non-endpoint actors.
IA-2 requires unique identification and authentication of organizational users before any channel use, blocking unauthenticated endpoint access.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.5.14 mandates rules/procedures/agreements (incl. recipient auth, crypto per 8.24, stronger auth on public nets, anti-interception/unauth-access controls) that stop non-endpoint actors from accessing/influencing the channel for most transfer forms; remainder (e.g. some verbal transfer, misrouting not caught by auth) is nameable.
Network security controls directly address channel integrity and endpoint authentication.
Security of network services includes measures to verify endpoints and protect channel integrity.
Cryptography provides channel integrity and can support endpoint authentication.
Secure authentication mechanisms verify actor identity at both ends of the channel.
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-300, a class-level weakness, and none of its children carries one either.