CVE-2023-34400
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMercedes-Benz head-unit NTG6 contains functions to import or export profile settings over USB. In case of parsing file, service try to define header inside the file and convert it to null-terminated string. If character is missed, will return null pointer.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Mercedes-Benz NTG6 head-unit contains a null pointer dereference vulnerability in its USB profile import/export functionality. When parsing a file header, the service attempts to convert the header to a null-terminated string, but if a character is missing from the header, it returns a null pointer instead of properly handling the error. An attacker could exploit this by providing a specially crafted USB device with a malformed profile file.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2021CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify NTG6 head-unit firmware versionAccess the head-unit's system settings or diagnostics menu to view the firmware version. On NTG6, this is typically found under Settings > System > Software Update or through the vehicle's service diagnostic port.Affected if The firmware version is from 2021 or earlier, indicating the unpatched version is installed
-
Verify USB profile feature is activeCheck if the head-unit's USB functionality includes profile import/export. This feature is typically accessible when a USB device is connected to the head-unit's USB port.Affected if USB profile import/export functionality is available and enabled on the head-unit
-
Inspect connected USB devicesReview any USB devices that have been connected to the vehicle's head-unit. Check for profile files that may have been imported from USB devices.Affected if Untrusted or unknown USB devices have been connected to the head-unit's USB port
-
Examine USB profile configuration filesIf accessible through service diagnostics, review the profile configuration data stored on the head-unit for any anomalies or malformed entries.Affected if Malformed profile data exists on the head-unit or was attempted to be imported from a USB device
The user is affected if they have an NTG6 head-unit with 2021 or earlier firmware and USB profile import/export functionality is enabled, with potential exposure to untrusted USB devices.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the Mercedes-Benz security update for NTG6 head-unit once released. Until then, avoid connecting untrusted USB devices to the vehicle's head-unit.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34400 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-34400 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data