LiveActive security incident?Get immediate response
CVE Record

CVE-2023-34403: Mercedes-Benz head-unit NTG6 has Ethernet pins on Base Board to connect module CSB.

Mercedes-Benz head-unit NTG6 has Ethernet pins on Base Board to connect module CSB. Attacker can connect to this pins and get access to internal network. A race condition can be acquired and attacker can spoof “UserData” with desirable file path and access it though backup on USB.

MediumCVSS 4.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE describes a Mercedes-Benz NTG6 head-unit weakness where access to exposed Ethernet pins on the base board may let an attacker reach an internal vehicle network and access data through USB backup behavior. It is not described as remotely exploitable from the internet.

Executive priority

Prioritize for fleets, high-value vehicles, and vehicles exposed to untrusted servicing or physical access. This is not presented as a mass internet-exploitation issue, but it can affect vehicle internal-network trust and data access where NTG6 head units are in scope.

Technical view

The source describes Ethernet pins on the NTG6 base board connecting to the CSB module. With required access and privileges, a race condition may allow spoofing “UserData” with a chosen file path, then accessing it via USB backup. CVSS is 4.9, with adjacent attack vector and user interaction required.

Likely exposure

Exposure appears limited to environments with Mercedes-Benz NTG6 head units, but the CVE bundle lists affected vendor, product, and versions as n/a. Fleet owners, repair workflows, and vehicles with untrusted physical access are the most relevant concern.

Exploitation context

The bundle does not cite KEV listing or active exploitation. The described attack depends on access to head-unit hardware pins, a race condition, and USB backup behavior, so it is more plausible in targeted physical or service-access scenarios than broad remote attacks.

Researcher notes

Key gaps are affected models, firmware versions, and vendor remediation status. The public record supports CWE-284, CVSS 4.9, adjacent access, low complexity, low privileges, user interaction, and low confidentiality, integrity, and availability impact. Avoid assuming broader Mercedes-Benz product exposure without vendor confirmation.

Mitigation direction

  • Check Mercedes-Benz or authorized service guidance for updates or repair actions.
  • Restrict unsupervised physical access to vehicles and head-unit service areas.
  • Control and log USB media use in fleet service workflows.
  • Inspect vehicles for signs of head-unit tampering after untrusted access.
  • Apply firmware or software updates only when vendor guidance identifies them.

Validation and detection

  • Inventory vehicles or lab units using Mercedes-Benz NTG6 head units.
  • Confirm whether Mercedes-Benz has issued model-specific service guidance.
  • Review service records for head-unit removal, tampering, or unexplained USB backup activity.
  • Validate fleet procedures restrict untrusted USB devices and service access.
  • Track CVE metadata because affected version data is incomplete.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-34403 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.9CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L1.53.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.9Medium
CVSS 3.1 vector shape for CVE-2023-34403Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.