Authorization bypass via unchecked HS256 signatures
Published Feb 1, 2023 · Updated Mar 10, 2025
Improper JWS signature verification in OCaml-JOSE before 0.8.2 allows remote attackers to bypass authorization with forged HS256 tokens. In Jose.Jws.validate, the HS256 path hashes the supplied signature and compares it with a plain SHA-256 digest of the signing input instead of comparing the signature with a keyed HMAC over that input. A reachable service is exposed when it relies on JWS claims without additional checks, allowing altered header or payload claims to cross its authorization boundary.
Summary
What happened
Improper JWS signature verification in OCaml-JOSE before 0.8.2 allows remote attackers to bypass authorization with forged HS256 tokens. In Jose.Jws.validate, the HS256 path hashes the supplied signature and compares it with a plain SHA-256 digest of the signing input instead of comparing the signature with a keyed HMAC over that input. A reachable service is exposed when it relies on JWS claims without additional checks, allowing altered header or payload claims to cross its authorization boundary.
The record
- CVE
- CVE-2023-23928
- Published
- Feb 1, 2023
- Updated
- Mar 10, 2025
- Vendor
- Ulrik Strid
- Product
- OCaml-JOSE
- Classifications
- CWE-347, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 1, 2023CVE publishedPublication date reported by the CVE source.
- Mar 10, 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=< 0.8.2
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