Sensitive data exposure via AES ECB initialization
Published Nov 9, 2023 · Updated Sep 4, 2024
Inadequate encryption strength in esptool 4.6.2 and earlier allows attackers to expose sensitive data through AES ECB processing. The two reported loci in espsecure/init.py initialize AES in ECB mode rather than a randomized or authenticated mode. The public report supplies no command, proof of concept, or attacker-controlled input, so the required access path and specific exposed data remain undisclosed.
Summary
What happened
Inadequate encryption strength in esptool 4.6.2 and earlier allows attackers to expose sensitive data through AES ECB processing. The two reported loci in espsecure/init.py initialize AES in ECB mode rather than a randomized or authenticated mode. The public report supplies no command, proof of concept, or attacker-controlled input, so the required access path and specific exposed data remain undisclosed.
The record
- CVE
- CVE-2023-46894
- Published
- Nov 9, 2023
- Updated
- Sep 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-326
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 9, 2023CVE publishedPublication date reported by the CVE source.
- Sep 4, 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