LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19563: A misconfiguration in the debug interface in Mercedes-Benz HERMES 2.1 allows an attacker with direct physic...

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This issue concerns a Mercedes-Benz HERMES 2.1 device debug interface that was misconfigured. Someone with direct physical access to the device hardware could obtain cellular modem information. The public record does not describe remote exploitation, affected vehicle models, or a confirmed patch.

Executive priority

Handle as a targeted physical-access exposure, not an internet-scale emergency. Prioritize fleets with uncontrolled vehicle custody, third-party servicing, or high-value operational privacy concerns. Vendor confirmation is necessary before planning technical remediation.

Technical view

CVE-2019-19563 is an information-disclosure issue in the HERMES 2.1 debug interface. The required attack condition is direct physical hardware access. The disclosed data is described only as cellular modem information. No CVSS, CWE, product CPE, exploit activity, or remediation detail is provided in the source bundle.

Likely exposure

Exposure is most relevant to organizations operating Mercedes-Benz assets that contain HERMES 2.1 hardware. Public sources do not identify specific vehicle models, years, regions, or deployment configurations, so asset confirmation requires vendor or internal fleet documentation.

Exploitation context

The source bundle does not support active exploitation. The vulnerability requires physical access to device hardware, which limits scale but matters for vehicles or components exposed to theft, repair chains, resale, or uncontrolled physical custody.

Researcher notes

The public CVE text is sparse: no CVSS, CWE, affected CPEs, exploit status, or fix details are included. Avoid broad model-year claims. Analysis should stay limited to HERMES 2.1, physical hardware access, and cellular modem information disclosure.

Mitigation direction

  • Confirm with Mercedes-Benz guidance whether any HERMES 2.1 update or service action exists.
  • Restrict physical access to affected vehicles, telematics units, and spare hardware.
  • Review repair, resale, and decommissioning handling for telematics components.
  • Treat modem identifiers as sensitive asset data in inventory and incident workflows.

Validation and detection

  • Inventory vehicles or components that use Mercedes-Benz HERMES 2.1 hardware.
  • Check vendor service records for related telematics or HERMES remediation actions.
  • Assess whether debug interfaces are accessible during maintenance or hardware handling.
  • Document any confirmed exposure because public affected-product data is incomplete.
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-19563 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.