Authentication bypass via fixed JWT signing secret
Published Oct 17, 2022 · Updated May 10, 2025
Authentication bypass in anji-plus AJ-Report 0.9.8.6 allows remote authenticated users to impersonate users with forged JWT tokens. JwtBean#createToken uses a fixed signing secret, while TokenFilter accepts a token whose username selects the Redis login entry without binding its UUID. A low-privilege account with a login token from the preceding hour satisfies the gate; changing the username claim grants another user's access.
Summary
What happened
Authentication bypass in anji-plus AJ-Report 0.9.8.6 allows remote authenticated users to impersonate users with forged JWT tokens. JwtBean#createToken uses a fixed signing secret, while TokenFilter accepts a token whose username selects the Redis login entry without binding its UUID. A low-privilege account with a login token from the preceding hour satisfies the gate; changing the username claim grants another user's access.
The record
- CVE
- CVE-2022-42983
- Published
- Oct 17, 2022
- Updated
- May 10, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-290
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 17, 2022CVE publishedPublication date reported by the CVE source.
- May 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?
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
- AJ-Report forged JWT reproductionproof 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