LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19557: A misconfiguration in the debug interface in Mercedes-Benz HERMES 1 allows an attacker with direct physical...

A misconfiguration in the debug interface in Mercedes-Benz HERMES 1 allows an attacker with direct physical access to device hardware to obtain cellular modem information.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-19557 concerns a misconfigured debug interface in Mercedes-Benz HERMES 1 hardware. A person with direct physical access could obtain cellular modem information. The public bundle does not provide CVSS scoring, affected vehicle models, or a confirmed fix, so urgency depends on whether exposed fleets contain this hardware.

Executive priority

Treat this as a targeted physical-access information-disclosure risk, not a confirmed remote emergency. Prioritize scoping for fleets or labs with Mercedes-Benz HERMES 1 exposure, then seek vendor confirmation on remediation and affected models.

Technical view

The CVE describes a debug-interface misconfiguration in Mercedes-Benz HERMES 1 that permits cellular modem information disclosure when an attacker has direct physical access to device hardware. No CWE, CPE, affected version range, CVSS vector, patch detail, or exploit method is provided in the supplied sources.

Likely exposure

Exposure appears limited to environments with Mercedes-Benz HERMES 1 hardware and realistic direct physical access risk. The sources do not identify specific vehicle models, production years, firmware versions, or CPEs, so asset confirmation is required before scoping business impact.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. The described prerequisite is direct physical access to the device hardware, which lowers broad remote risk but matters for fleet, resale, service, theft, or lab-access scenarios.

Researcher notes

The public record is sparse. The core claim is modem information exposure through a debug-interface misconfiguration with physical access. Avoid extrapolating to remote compromise, broader vehicle control, or specific Mercedes-Benz models unless confirmed by additional vendor or research documentation.

Mitigation direction

  • Check Mercedes-Benz or Daimler guidance for affected HERMES 1 hardware and remediation status.
  • Restrict physical access to vehicles, telematics units, spare parts, and service benches.
  • Ask fleet, service, or OEM contacts whether HERMES 1 units remain deployed.
  • Track this CVE in vulnerability management until vendor remediation evidence is available.

Validation and detection

  • Inventory vehicles or components that may contain Mercedes-Benz HERMES 1 hardware.
  • Review service records, telematics bills, and OEM documentation for HERMES 1 references.
  • Confirm whether debug interfaces are disabled or access-controlled through authorized hardware assessment.
  • Document uncertainty where model, firmware, or patch status cannot be verified.
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.

cve · low confidence lookup

CVE-2019-19557 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.