Source-code disclosure via static RSA key
Published May 8, 2023 · Updated Jan 29, 2025
Hard-coded key use in AXIS OS 11.0.x through 11.3.x allows remote authenticated users to read non-sensitive legacy LUA source code. Legacy LUA components encrypt Axis-specific source with one static RSA key, so possession of that key defeats only the code-obfuscation layer. Network reachability and high privileges are required; Axis states that the key protects no sensitive data and cannot compromise devices or customer data.
Summary
What happened
Hard-coded key use in AXIS OS 11.0.x through 11.3.x allows remote authenticated users to read non-sensitive legacy LUA source code. Legacy LUA components encrypt Axis-specific source with one static RSA key, so possession of that key defeats only the code-obfuscation layer. Network reachability and high privileges are required; Axis states that the key protects no sensitive data and cannot compromise devices or customer data.
The record
- CVE
- CVE-2023-21404
- Published
- May 8, 2023
- Updated
- Jan 29, 2025
- Vendor
- Axis Communications AB
- Product
- AXIS OS
- Classifications
- CWE-311, CWE-321
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 8, 2023CVE publishedPublication date reported by the CVE source.
- Jan 29, 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=AXIS OS 11.0.X - 11.3.x
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