Unauthenticated account impersonation via hard-coded JWT key
Published Apr 19, 2022 · Updated Apr 22, 2025
Hard-coded key use in vran-dev Databasir allows remote attackers to forge JWTs and impersonate any user. JwtTokens signs and verifies HMAC256 tokens with the same source-embedded secret, while getUsername trusts the username claim after signature verification. Knowledge of the published key permits unauthenticated access to another deployment's administrative backend as an arbitrary account, bounded by that account's privileges.
Summary
What happened
Hard-coded key use in vran-dev Databasir allows remote attackers to forge JWTs and impersonate any user. JwtTokens signs and verifies HMAC256 tokens with the same source-embedded secret, while getUsername trusts the username claim after signature verification. Knowledge of the published key permits unauthenticated access to another deployment's administrative backend as an arbitrary account, bounded by that account's privileges.
The record
- CVE
- CVE-2022-24860
- Published
- Apr 19, 2022
- Updated
- Apr 22, 2025
- Vendor
- vran-dev
- Product
- Databasir
- Classifications
- CWE-798, CWE-321, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 19, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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=> 1.0.1
What conditions does exploitation require?
What is affected?
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
- Upstream JWT forgery demonstrationproof 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