Remote Phy 120 FirmwareOperating system · Cisco
CVE-2019-1839
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 · uneditedA vulnerability in Cisco Remote PHY Device Software could allow an authenticated, local attacker to execute commands on the underlying Linux shell of an affected device with root privileges. The vulnerability occurs because the affected software improperly sanitizes user-supplied input. An attacker who has valid administrator access to an affected device could exploit this vulnerability by supplying various CLI commands with crafted arguments. A successful exploit could allow the attacker to run arbitrary commands as the root user, allowing complete compromise of the system.
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 · high confidenceCommand injection vulnerability in Cisco Remote PHY Device Software allows authenticated administrators to execute arbitrary Linux commands with root privileges by supplying crafted arguments to CLI commands. The root cause is improper sanitization of user-supplied input in the CLI parsing logic.
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
Remote Phy 120 FirmwareOperating system
< 6.4
Remote Phy 220 FirmwareOperating system
< 3.1
Remote Phy Shelf 7200 FirmwareOperating system
< 1.2
Cbr 8 FirmwareOperating system
= 1.1= 6.1= 6.2CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 the Cisco Remote PHY device modelAccess the device CLI or web interface and run 'show version' or check the device inventory to confirm the exact model (Remote PHY 120, Remote PHY 220, Remote PHY Shelf 7200, or CBR-8)Affected if The device is one of these four models
-
Determine the installed firmware versionRun 'show version' or 'show software version' in the device CLI to retrieve the current firmware version numberAffected if The version cannot be determined or is not visible
-
Compare version for Cisco Remote PHY 120If the device is a Remote PHY 120, check if the firmware version is less than 6.4 (for example, 6.3.x, 6.2.x, etc.)Affected if Version < 6.4
-
Compare version for Cisco Remote PHY 220If the device is a Remote PHY 220, check if the firmware version is less than 3.1 (for example, 3.0.x, 2.x, etc.)Affected if Version < 3.1
-
Compare version for Cisco Remote PHY Shelf 7200If the device is a Remote PHY Shelf 7200, check if the firmware version is less than 1.2 (for example, 1.1.x, 1.0.x, etc.)Affected if Version < 1.2
-
Compare version for Cisco CBR-8If the device is a CBR-8, check if the firmware version is exactly 1.1, 6.1, or 6.2Affected if Version equals 1.1, 6.1, or 6.2
The device is affected if it matches one of the four product models AND its firmware version falls within the specified vulnerable version range or exact versions.
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 data1.23.16.4
Apply Cisco's patch for this vulnerability when available. Restrict administrative access to trusted personnel only, and implement least-privilege access controls. Monitor administrative sessions for unusual command patterns.
Fix this in Remote Phy 120 Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1839 — 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-1839 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