TLS secret disclosure via hard-coded AES key
Published Dec 27, 2023 · Updated Nov 26, 2024
Hard-coded AES key use in Phlox Simple HTTP Server 1.8 and Simple HTTP Server PLUS 1.8.1-plus allows local users to decrypt TLS secrets. The SecretKeySpec constructor initializes AES with the same embedded byte string in the application, so extracting the binary reveals the key protecting its TLS secret. Physical access to the application binary or source is required; possession of the key exposes protected data and enables interception or modification in transit.
Summary
What happened
Hard-coded AES key use in Phlox Simple HTTP Server 1.8 and Simple HTTP Server PLUS 1.8.1-plus allows local users to decrypt TLS secrets. The SecretKeySpec constructor initializes AES with the same embedded byte string in the application, so extracting the binary reveals the key protecting its TLS secret. Physical access to the application binary or source is required; possession of the key exposes protected data and enables interception or modification in transit.
The record
- CVE
- CVE-2023-46919
- Published
- Dec 27, 2023
- Updated
- Nov 26, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-321, CWE-798, T1552.001
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 27, 2023CVE publishedPublication date reported by the CVE source.
- Nov 26, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Hard-coded AES key disclosureproof 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