# CVE-2019-19557: Information disclosure in n/a

> An attacker with physical access can exploit a debug interface misconfiguration to extract cellular modem information from the device.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p9q6-mf27-x2fp

## What is CVE-2019-19557?

CVE-2019-19557 is a low-severity vulnerability in n/a, published on 15 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

## Which versions are affected by CVE-2019-19557?

It affects 1 product.


Products: Harman Hermes.

## How do I fix CVE-2019-19557?

No fix has been published for CVE-2019-19557 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-19557 being exploited?

There is no known exploitation of CVE-2019-19557 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-19556](https://insights.sbomify.com/CVE-2019-19556/): Auth bypass in n/a (medium 4.6)
- [CVE-2019-19560](https://insights.sbomify.com/CVE-2019-19560/): Auth bypass in n/a (medium 4.6)
- [CVE-2019-19562](https://insights.sbomify.com/CVE-2019-19562/): Auth bypass in n/a (medium 4.6)
- [CVE-2019-19561](https://insights.sbomify.com/CVE-2019-19561/): Information disclosure in n/a (low 2.4)
- [CVE-2019-19563](https://insights.sbomify.com/CVE-2019-19563/): Information disclosure in n/a (low 2.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19557 and fix it if it is affected.

What it is: CVE-2019-19557 is a low-severity vulnerability in n/a, published on 15 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19557 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-19557/ (Markdown: https://insights.sbomify.com/CVE-2019-19557/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-19557
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-19557
- OSV: https://osv.dev/vulnerability/CVE-2019-19557

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-19557/
Summaries are generated and may contain mistakes; the official description above is the record.