Message decryption via static hardcoded transport key
Published Aug 22, 2024 · Updated Oct 31, 2024
Hardcoded-key cryptography in UCI Software IDOL2 2.12 and earlier allows attackers to decrypt intercepted client-server messages. The transport key is deterministically derived from a static copyright string and reused for symmetric encryption, allowing captured ciphertext to be decrypted or forged. Exploitation requires access to client-server traffic; message confidentiality is affected, while integrity and availability impact remain unestablished.
Summary
What happened
Hardcoded-key cryptography in UCI Software IDOL2 2.12 and earlier allows attackers to decrypt intercepted client-server messages. The transport key is deterministically derived from a static copyright string and reused for symmetric encryption, allowing captured ciphertext to be decrypted or forged. Exploitation requires access to client-server traffic; message confidentiality is affected, while integrity and availability impact remain unestablished.
The record
- CVE
- CVE-2024-45165
- Published
- Aug 22, 2024
- Updated
- Oct 31, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-321, CWE-798, T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2024CVE publishedPublication date reported by the CVE source.
- Oct 31, 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
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