Server takeover via improper certificate validation
Published Feb 7, 2024 · Updated Nov 3, 2025
Improper certificate validation in IBM Security Verify Access 10.0.0.0 through 10.0.6.1 allows attackers to take control from adjacent networks. IBM identifies insecure calls as the affected locus but does not disclose which call accepts an untrusted certificate or endpoint. No credentials or user interaction are required, but exploitation requires an adjacent network position and high-complexity conditions; success compromises the server.
Summary
What happened
Improper certificate validation in IBM Security Verify Access 10.0.0.0 through 10.0.6.1 allows attackers to take control from adjacent networks. IBM identifies insecure calls as the affected locus but does not disclose which call accepts an untrusted certificate or endpoint. No credentials or user interaction are required, but exploitation requires an adjacent network position and high-complexity conditions; success compromises the server.
The record
- CVE
- CVE-2023-32330
- Published
- Feb 7, 2024
- Updated
- Nov 3, 2025
- Vendor
- IBM
- Product
- IBM Security Verify Access Appliance
- Classifications
- CWE-295, T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 7, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.0.0 <=10.0.6.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo