Adjacent-network code execution via unvalidated Content-Length
Published Jul 30, 2025 · Updated Jul 30, 2025
Remote code execution in Tesla Wall Connector 24.44.1 allows network-adjacent attackers to execute arbitrary code via crafted HTTP requests. The HTTP Content-Length parser accepts an unvalidated attacker-controlled length and accesses memory beyond the allocated request buffer. Exploitation requires no authentication or user interaction but does require adjacent-network access, and successful exploitation runs code in the device context.
Summary
What happened
Remote code execution in Tesla Wall Connector 24.44.1 allows network-adjacent attackers to execute arbitrary code via crafted HTTP requests. The HTTP Content-Length parser accepts an unvalidated attacker-controlled length and accesses memory beyond the allocated request buffer. Exploitation requires no authentication or user interaction but does require adjacent-network access, and successful exploitation runs code in the device context.
The record
- CVE
- CVE-2025-8320
- Published
- Jul 30, 2025
- Updated
- Jul 30, 2025
- Vendor
- Tesla
- Product
- Wall Connector
- Classifications
- CWE-1284, T1190
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2025CVE publishedPublication date reported by the CVE source.
- Jul 30, 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=24.44.1
What conditions does exploitation require?
What is affected?
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