Authenticated access-control bypass via unverified token claims
Published May 20, 2020 · Updated Sep 16, 2024
Improper id_token validation in IBM Security Verify Access Appliance 9.0.7.1 allows remote authenticated users to bypass access controls. The id_token processing path accepts attacker-manipulated claims without verifying their authenticity before applying them to access-control decisions. A valid appliance account is required; IBM reports integrity impact only and does not disclose the affected endpoint or claim-processing function.
Summary
What happened
Improper id_token validation in IBM Security Verify Access Appliance 9.0.7.1 allows remote authenticated users to bypass access controls. The id_token processing path accepts attacker-manipulated claims without verifying their authenticity before applying them to access-control decisions. A valid appliance account is required; IBM reports integrity impact only and does not disclose the affected endpoint or claim-processing function.
The record
- CVE
- CVE-2020-4461
- Published
- May 20, 2020
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Security Verify Access Appliance
- Classifications
- T1548
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record 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=9.0.7.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.
Weakness, pattern, technique
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