CVE-2019-17584
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMeinberg SyncBox/PTP/PTPv2 devices contain hardcoded/default SSH private keys that allow remote attackers to gain root access. The private key can be extracted from firmware updates of related Meinberg devices, enabling unauthenticated remote compromise of affected devices.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.34o< 5.34s< 5.32< 5.34gCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the device management interface or use network discovery to confirm the device is a Meinberg SyncBox, PTP, or PTPv2 device. Check the device's web interface, console, or SNMP information for the model designation.Affected if The device is a Meinberg SyncBox, PTP, or PTPv2 model.
-
Check firmware versionLog into the device management interface or use the CLI (SSH or console) to retrieve the firmware version. Navigate to the system status or firmware information section. Compare your installed version against the affected ranges: < 5.34o, < 5.34s, < 5.32, < 5.34g.Affected if The installed firmware version is lower than 5.34o, 5.34s, 5.32, or 5.34g.
-
Verify SSH access statusConfirm whether SSH is enabled and accessible on the device. Check the device configuration settings for SSH service status. Attempt a connection to port 22 (or the configured SSH port) from a management network.Affected if SSH is enabled and reachable on the network.
-
Inspect SSH key configurationIf you have administrative access to the device, examine the SSH server configuration and installed authorized_keys. Look for any default, manufacturer-embedded, or static SSH private keys in the device firmware or configuration.Affected if Default or hardcoded SSH keys are present in the device configuration.
The environment is affected if it contains a Meinberg SyncBox/PTP/PTPv2 device running firmware version below 5.34o/5.34s/5.32/5.34g with SSH access enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data5.325.34o5.34s
Update firmware to the patched version (v5.34o, v5.34s, v5.32*, or 5.34g or later) per vendor guidance. If immediate patching is not feasible, disable or restrict SSH access through network controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17584 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-17584 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data