Authentication bypass via hard-coded JWT signing key
Published Aug 20, 2024 · Updated Aug 20, 2024
Hard-coded credentials in demozx gf_cms 1.0 and 1.0.1 allow remote attackers to forge JWTs and access protected functions. The JWT middleware initialized in internal/logic/auth/auth.go signs and validates tokens with the literal key "secret key," exposing the same secret in every deployment. No authentication or user interaction is required; knowledge of the published key permits accepted bearer tokens carrying attacker-selected identity claims.
Summary
What happened
Hard-coded credentials in demozx gf_cms 1.0 and 1.0.1 allow remote attackers to forge JWTs and access protected functions. The JWT middleware initialized in internal/logic/auth/auth.go signs and validates tokens with the literal key "secret key," exposing the same secret in every deployment. No authentication or user interaction is required; knowledge of the published key permits accepted bearer tokens carrying attacker-selected identity claims.
The record
- CVE
- CVE-2024-8005
- Published
- Aug 20, 2024
- Updated
- Aug 20, 2024
- Vendor
- demozx
- Product
- gf_cms
- Classifications
- CWE-798, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2024CVE publishedPublication date reported by the CVE source.
- Aug 20, 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.0
- 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.
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