Privilege escalation via JWT signature bypass
Published Feb 8, 2024 · Updated Jun 17, 2025
JWT authentication bypass in Egerie Risk Manager 4.0.5 allows remote authenticated users to escalate privileges through a modified token. The server accepts altered authorization values in a JWT payload without enforcing the token's signature, allowing claims to be changed after issuance. A low-privileged account and network access are required; successful tampering grants the application privileges assigned by the forged claims.
Summary
What happened
JWT authentication bypass in Egerie Risk Manager 4.0.5 allows remote authenticated users to escalate privileges through a modified token. The server accepts altered authorization values in a JWT payload without enforcing the token's signature, allowing claims to be changed after issuance. A low-privileged account and network access are required; successful tampering grants the application privileges assigned by the forged claims.
The record
- CVE
- CVE-2023-27001
- Published
- Feb 8, 2024
- Updated
- Jun 17, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 8, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Post Cyber Labs JWT payload-tampering proof of conceptproof of concept · unverified
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