Safeguard
Vulnerability Analysis•

CVE-2023-31004: High MITM Flaw in IBM Security Verify Access

CVE-2023-31004 is a High (CVSS 8.3) man in the middle flaw in IBM Security Verify Access up to 10.0.6.1. Apply fix pack 10.0.7 or the latest container.

Safeguard Security Team
3 min read

CVE-2023-31004 is a high severity (CVSS 8.3) man in the middle flaw in IBM Security Verify Access, formerly Security Access Manager. A remote attacker using such techniques could reach the underlying system. IBM's remedy is fix pack 10.0.7 on appliances, or the latest container tag.

What's affected

IBM's bulletin 7106586 lists IBM Security Verify Access Appliance and Docker 10.0.0.0 through 10.0.6.1 as affected. IBM's vector for this entry has an adjacent network attack vector with high attack complexity and a changed scope. IBM's remediation is to pull the latest published container tag, and for appliances to install fix pack 10.0.7-ISS-ISVA-FP0000, which IBM lists for IBM Security Verify Access 10.0.0.0. IBM lists no workarounds or mitigations.

A later IBM bulletin (7158790) covers release 10.0.8.0. Check it as well, since it may carry newer fixes for this product line.

How to check if you're exposed

For the container, list the image tag you are running:

docker ps --format "table {{.Names}}\t{{.Image}}"

Compare the tag with the affected range. IBM's remediation for the container is to pull the latest published tag:

docker pull icr.io/isva/verify-access:TAG

Replace TAG with the latest version listed on IBM's page. For appliances, read the firmware version in the appliance management interface. This is a device or appliance issue, not a package you pull from a registry, so a dependency scan will not see it. Safeguard's free in-browser scan at https://gold.safeguard.sh/scan reads dependency manifests and will not detect firmware running on hardware. Use your asset inventory instead.

What to do now

  1. Identify every IBM Security Verify Access (formerly Security Access Manager) appliance and container you run, and record the version.
  2. Apply the fix IBM lists: pull the latest container tag, or install the fix pack for appliances.
  3. Treat IBM's bulletin as the source for the current fix, and check it for newer releases.

Why it matters

The class is CWE-300, a channel accessible by non endpoint. In practice that means traffic between two parties can be observed or changed by someone in between. IBM says the attacker could gain access to the underlying system.

The adjacent vector means the attacker needs to be on the same network segment as the appliance or its peers. That limits exposure, but segments in data centres are often flatter than people expect. Encrypting and authenticating internal links, and patching, are the usual remedies. The CVE is not on the CISA KEV list.

While you schedule the update, check where this product sits on your network and who else shares the segment. An adjacent attacker needs a foothold nearby, such as a compromised server or a workstation on the same VLAN. Tightening those paths with segmentation and access lists reduces exposure even before the patch lands.

Quick check

Does the attacker need to be on the internet?

No. The vector is adjacent network, so the attacker must be on a reachable segment.

Why is complexity high?

IBM's vector rates attack complexity as high, which lowers the score from what it would otherwise be.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.