LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19556: An authentication bypass in the debug interface in Mercedes-Benz HERMES 1 allows an attacker with physical...

An authentication bypass in the debug interface in Mercedes-Benz HERMES 1 allows an attacker with physical access to device hardware to obtain system information.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-19556 is an authentication bypass in the debug interface of Mercedes-Benz HERMES 1. The documented impact is disclosure of system information, and the attacker needs physical access to device hardware. This is not a broad remote compromise based on the provided sources, but it matters for fleets, service environments, and hardware custody.

Executive priority

Prioritize this for Mercedes-Benz fleets, service centers, and hardware custody programs. It is lower urgency than internet-exposed remote flaws, but weak physical debug protection can undermine confidentiality and support follow-on analysis if hardware leaves trusted control.

Technical view

The CVE describes unauthenticated access through a HERMES 1 debug interface, allowing system information retrieval when the attacker can physically access the hardware. The source bundle does not provide CVSS, CWE, fixed versions, detailed affected model coverage, or a named vendor patch. Treat exposure analysis as asset-specific.

Likely exposure

Exposure appears limited to Mercedes-Benz HERMES 1 hardware with physically reachable debug interfaces. The provided CVE metadata does not identify affected vehicle models, firmware versions, or CPEs, so owners should confirm applicability through Mercedes-Benz or Daimler support channels.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, or public weaponized exploitation. The required condition is physical access to the device hardware, which makes abuse more plausible in theft, repair, teardown, resale, or insider-access scenarios than across the internet.

Researcher notes

Evidence is sparse: no CVSS, CWE, CPE, fixed version, or detailed exploit narrative is included in the source bundle. The key confirmed points are authentication bypass, debug interface, HERMES 1, physical access requirement, and system information exposure.

Mitigation direction

  • Check Mercedes-Benz or Daimler guidance for affected HERMES 1 units and fixes.
  • Restrict physical access to telematics hardware and service interfaces.
  • Use vendor-approved procedures to disable, lock, or protect debug interfaces where available.
  • Review service-chain custody controls for vehicles or removed telematics units.
  • Document compensating controls if vendor remediation is unavailable.

Validation and detection

  • Inventory vehicles or hardware that may contain Mercedes-Benz HERMES 1.
  • Confirm whether physical debug interfaces are reachable during normal service handling.
  • Review vendor bulletins or support responses for affected versions and remediation status.
  • Verify service providers follow controls for telematics hardware access.
  • Record evidence when systems are confirmed not applicable.
Prepared
Confidence
medium
Sources
4

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.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-19556 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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