Head-unit crash via malformed USB profile archive
Published Feb 13, 2025 · Updated Mar 18, 2025
A null pointer dereference in Mercedes-Benz NTG6 profile import allows physically proximate attackers to crash the head unit via USB. The profile-import path passes serialized table values to Boost archive deserialization, where malformed data triggers a null pointer dereference. Physical access to the vehicle and interaction with its exposed USB import service are required, and the reported consequence is loss of availability.
Summary
What happened
A null pointer dereference in Mercedes-Benz NTG6 profile import allows physically proximate attackers to crash the head unit via USB. The profile-import path passes serialized table values to Boost archive deserialization, where malformed data triggers a null pointer dereference. Physical access to the vehicle and interaction with its exposed USB import service are required, and the reported consequence is loss of availability.
The record
- CVE
- CVE-2023-34398
- Published
- Feb 13, 2025
- Updated
- Mar 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 13, 2025CVE publishedPublication date reported by the CVE source.
- Mar 18, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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