Token forgery via hard-coded verification key
Published Feb 27, 2024 · Updated Aug 1, 2024
Hard-coded key use in LightPicture 1.2.0 through 1.2.2 allows remote attackers to compromise token verification without authentication. The handle function in app/middleware/TokenVerify.php verifies attacker-supplied tokens with a cryptographic key embedded in application code. Exploitation requires high complexity and no user interaction; published records do not define the exact resulting access.
Summary
What happened
Hard-coded key use in LightPicture 1.2.0 through 1.2.2 allows remote attackers to compromise token verification without authentication. The handle function in app/middleware/TokenVerify.php verifies attacker-supplied tokens with a cryptographic key embedded in application code. Exploitation requires high complexity and no user interaction; published records do not define the exact resulting access.
The record
- CVE
- CVE-2024-1920
- Published
- Feb 27, 2024
- Updated
- Aug 1, 2024
- Vendor
- osuuu
- Product
- LightPicture
- Classifications
- CWE-321, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.2.0
- Affected versionversion=1.2.1
- Affected versionversion=1.2.2
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.
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