CVE-2023-32328 is a high severity flaw, scored 7.5, where IBM Security Verify Access 10.0.0.0 through 10.0.6.1 uses insecure protocols in some instances. An attacker on the network could take control of the server. IBM lists fix pack 10.0.7-ISS-ISVA-FP0000 as the remedy.
What's affected
IBM says Verify Access 10.0.0.0 through 10.0.6.1 uses insecure protocols in some instances that could allow an attacker on the network to take control of the server. The weakness is CWE-319 (cleartext transmission of sensitive information). The record is dated 2024-02-07, scored 7.5 with the vector CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. IBM tracks it as X-Force ID 254957.
IBM's bulletin lists one remedy for every issue in it: IBM Security Verify Access 10.0.0.0 through 10.0.6.1 should move to fix pack 10.0.7-ISS-ISVA-FP0000. For the Docker container, IBM says to pull the latest published tag of icr.io/isva/verify-access. The bulletin lists no workarounds or mitigations. Its initial publication date is 09 Jan 2024.
The IBM bulletin and the NVD record agree on the score and the affected range, 10.0.0.0 through 10.0.6.1. IBM's bulletin lists the vector with CVSS 3.0 where the record uses 3.1, and the values match. One detail does not line up: the NVD record description cites X-Force ID 254957, while its first reference link points to X-Force 254657. IBM's bulletin uses 254957.
No source says this flaw is exploited in the wild, and it is not in the CISA Known Exploited Vulnerabilities catalog.
How to check if you're exposed
For the appliance, open the administration console and read the firmware or fix pack level, then compare it with 10.0.7-ISS-ISVA-FP0000. Anything from 10.0.0.0 through 10.0.6.1 is in the affected range.
For containers, list the image tags you run:
docker images icr.io/isva/verify-access
Compare each tag with IBM's latest published tag. Also check Kubernetes manifests and compose files for pinned old tags, since a pinned tag keeps running the old code after a new one is published.
Include test and disaster recovery copies. Identity systems are often cloned for staging and then forgotten.
What to do now
- Inventory every IBM Security Verify Access appliance and container, with versions.
- Plan the move to 10.0.7-ISS-ISVA-FP0000 for appliances and the latest published tag for containers.
- Snapshot or back up configuration first. Access management is on the login path for other systems, so schedule a maintenance window.
- Restrict network access to management interfaces to an admin network.
- After updating, confirm the version in the console and record the change.
Why it matters
CWE-319 means data or commands travel over a channel that does not protect them, so someone positioned on the path can read or alter them. The vector says the attacker must be on an adjacent network and that the attack is hard to carry out, which keeps the score at 7.5 despite the full impact on confidentiality, integrity and availability.
IBM gives no detail on which protocols or connections are involved, and this post does not guess. What you can do is shrink the number of people who can sit between the product and its peers: put the system on a segmented network, and keep management traffic off shared segments. Safeguard offers a free in-browser dependency scan at gold.safeguard.sh/scan for the packages in your own code. It does not inspect commercial appliances or enterprise suites, so those need a vendor driven inventory.
Quick check
Can an attacker reach this over the internet?
The vector is adjacent network (AV:A), so the attacker needs a position on the same network segment or path. Keep management and peer traffic on isolated networks.
Which protocols are affected?
IBM does not say. The bulletin states only that insecure protocols are used in some instances.
Sources
Last reviewed: 19 October 2026.