CVE-2024-37600
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 · uneditedAn issue was discovered in Mercedes Benz NTG (New Telematics Generation) 6 through 2021. A possible stack buffer overflow in the Service Broker service affects NTG 6 head units. To perform this attack, physical access to Ethernet pins of the head unit base board is needed. With a static IP address, an attacker can connect via the internal network to the Service Broker service. With prepared HTTP requests, an attacker can cause the Service-Broker service to fail.
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 confidenceA stack buffer overflow vulnerability exists in the Service Broker service of Mercedes Benz NTG 6 head units (model years through 2021). An attacker with physical access to the Ethernet pins on the head unit base board can configure a static IP address, connect to the internal network, and send crafted HTTP requests that overflow the stack buffer, causing the Service-Broker service to fail.
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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 head unit modelLocate the head unit in the vehicle and verify it is an NTG 6 (Mercedes Benz User Experience) model. Check the hardware label or system information for the model designation.Affected if The unit is NOT an NTG 6 model - if it is NTG 6, proceed to next check.
-
Determine model yearCheck the head unit's build date, firmware date, or vehicle information display for the model year. The vulnerability affects model years through 2021.Affected if The model year is 2021 or earlier and the head unit is NTG 6.
-
Locate Ethernet pins on base boardPhysically access the head unit base board and inspect for exposed Ethernet pins or test points that allow direct network connection to the internal vehicle network.Affected if Ethernet pins or test points are physically accessible on the base board.
-
Verify Service Broker service availabilityIf network access is established via the Ethernet pins, attempt to reach the Service Broker service endpoint or check if the service responds to network requests.Affected if The Service Broker service is running and accessible over the network interface.
-
Confirm HTTP request handlingSend a crafted HTTP request to the Service Broker service endpoint to observe if the service handles it and whether a buffer overflow condition can be triggered.Affected if The Service Broker service accepts HTTP requests and processes them without proper bounds checking.
A user is affected if they have an NTG 6 head unit from model year 2021 or earlier with physically accessible Ethernet pins on the base board and the Service Broker service running and reachable via network requests.
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 dataPrimary mitigations include restricting physical access to the head unit's Ethernet pins and implementing network segmentation for vehicle internal networks. A permanent fix requires Mercedes to release a firmware patch for the Service Broker service.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37600 — 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-2024-37600 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