Unauthorized backend access via skipped JWT verification
Published Sep 27, 2023 · Updated Sep 24, 2024
Improper authorization in APIcast's OIDC module allows remote attackers to access protected API backends with a JWT from another realm. A missing JWK is dereferenced before token verification, and the resulting error skips the remaining policy stage instead of rejecting the request. OIDC must be configured with separate realms; with routing enabled, the invalid token reaches the upstream and can expose or alter protected data.
Summary
What happened
Improper authorization in APIcast's OIDC module allows remote attackers to access protected API backends with a JWT from another realm. A missing JWK is dereferenced before token verification, and the resulting error skips the remaining policy stage instead of rejecting the request. OIDC must be configured with separate realms; with routing enabled, the invalid token reaches the upstream and can expose or alter protected data.
The record
- CVE
- CVE-2023-0456
- Published
- Sep 27, 2023
- Updated
- Sep 24, 2024
- Vendor
- 389 Directory Server
- Product
- Red Hat 3scale API Management
- Classifications
- CWE-285, CWE-862, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 27, 2023CVE publishedPublication date reported by the CVE source.
- Sep 24, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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
- Cross-realm JWT verification procedureproof of concept · demonstrated
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