Unauthenticated account access via exposed JWT signing key
Published Sep 7, 2022 · Updated Apr 23, 2025
Authentication bypass in KubeVela 1.4.0 through 1.4.10 and 1.5.0 through 1.5.2 allows remote attackers to forge user JWTs. The VelaUX APIServer signs user tokens with PlatformID while unauthenticated getSystemInfo returns that same value, making it a public JWT signing key. Network access to VelaUX is sufficient to mint accepted tokens and enter protected API routes as an arbitrary user without credentials.
Summary
What happened
Authentication bypass in KubeVela 1.4.0 through 1.4.10 and 1.5.0 through 1.5.2 allows remote attackers to forge user JWTs. The VelaUX APIServer signs user tokens with PlatformID while unauthenticated getSystemInfo returns that same value, making it a public JWT signing key. Network access to VelaUX is sufficient to mint accepted tokens and enter protected API routes as an arbitrary user without credentials.
The record
- CVE
- CVE-2022-36089
- Published
- Sep 7, 2022
- Updated
- Apr 23, 2025
- Vendor
- KubeVela
- Product
- KubeVela
- Classifications
- CWE-294, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 7, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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.4.0, < 1.4.11
- Affected versionversion=>= 1.5.0, < 1.5.3
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
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