# CVE-2019-17584: Hardcoded credentials in n/a

> Attackers can gain root access to Meinberg SyncBox/PTP devices using hardcoded default SSH keys, requiring a firmware upgrade to mitigate.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hjqg-vhp3-pqqp

## What is CVE-2019-17584?

CVE-2019-17584 is a high-severity vulnerability in n/a, published on 21 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Meinberg SyncBox/PTP/PTPv2 devices have default SSH keys which allow attackers to get root access to the devices. All firmware versions up to v5.34o, v5.34s, v5.32* or 5.34g are affected. The private key is also used in an internal interface of another Meinberg Device and can be extracted from a firmware update of this device. An update to fix the vulnerability was published by the vendor.

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

It affects 1 product.


Products: Meinbergglobal Syncbox\/Ptpv2 Firmware.

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

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

## Is CVE-2019-17584 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-17584 is a high-severity vulnerability in n/a, published on 21 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-17584 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-17584/ (Markdown: https://insights.sbomify.com/CVE-2019-17584/index.md)
```

## Sources

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

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