Security readout for executives and security teams
IBM Security Verify Access Appliance and Docker versions 10.0.0.0 through 10.0.6.1 can allow access to the underlying system through man-in-the-middle techniques. The business concern is serious because this product can sit near identity and access control workflows. Sources do not show KEV listing or confirmed active exploitation. Exposure is most likely in IBM Security Verify Access Appliance or Docker deployments running 10.0.0.0 through 10.0.6.1, especially where an attacker could intercept adjacent-network traffic. The provided affected data is limited and should be reconciled against IBM’s advisory. Treat this as a high-priority identity infrastructure issue. It is not presented as actively exploited, but successful exploitation could compromise confidentiality, integrity, and availability of the underlying system supporting access management. Mitigation focus: Identify all IBM Security Verify Access Appliance and Docker deployments and versions.; Check IBM advisory 7106586 for fixed levels and vendor-specific remediation.; Prioritize remediation for internet-adjacent, shared-network, or identity-critical deployments..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-300: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-31004 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H1.66Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.3HighVector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ibm.com/support/pages/node/7106586CVE reference · vendor-advisory
- https://exchange.xforce.ibmcloud.com/vulnerabilities/254765CVE reference · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Channel Accessible by Non-Endpoint
Channel Accessible by Non-Endpoint represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.