Prime InfrastructureApplication · Cisco
CVE-2019-15958
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 the REST API of Cisco Prime Infrastructure (PI) and Cisco Evolved Programmable Network Manager (EPNM) could allow an unauthenticated remote attacker to execute arbitrary code with root privileges on the underlying operating system. The vulnerability is due to insufficient input validation during the initial High Availability (HA) configuration and registration process of an affected device. An attacker could exploit this vulnerability by uploading a malicious file during the HA registration period. A successful exploit could allow the attacker to execute arbitrary code with root-level privileges on the underlying operating system. Note: This vulnerability can only be exploited during the HA registration period. See the Details section for more information.
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 confidenceThis CVE allows unauthenticated remote attackers to achieve root-level code execution on Cisco Prime Infrastructure and EPNM through insufficient input validation during the High Availability registration process. Attackers exploit this by uploading malicious files during the limited HA registration window, bypassing authentication to execute arbitrary commands with root privileges.
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
Prime InfrastructureApplication
< 3.4.2>= 3.5, < 3.5.1= 3.6
Evolved Programmable Network ManagerApplication
< 3.0.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 product and versionDetermine if Cisco Prime Infrastructure or EPNM is installed, then retrieve the installed version numberAffected if The installed version is Cisco Prime Infrastructure < 3.4.2, >= 3.5 and < 3.5.1, or = 3.6; or Cisco EPNM < 3.0.2
-
Confirm High Availability is in useCheck whether the High Availability feature has been configured or is in the process of being set up on the systemAffected if HA registration has been initiated or completed on a vulnerable version
-
Review HA registration exposureInspect network configuration to determine if the HA registration interface is accessible from untrusted or external networksAffected if HA registration interface is exposed to untrusted networks without proper access restrictions
-
Audit for unauthorized HA activityReview system and security logs for any unexpected or unauthorized HA configuration attempts, especially from unexpected source IP addressesAffected if Suspicious or unauthorized HA registration attempts are found in logs
A system is affected if it runs a vulnerable version of Cisco Prime Infrastructure or EPNM AND has HA enabled or accessible, particularly if exposed to untrusted networks where an attacker could exploit the HA registration process.
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.
dbcve · scoped3.0.23.4.23.5.1
Restrict network access to HA registration interfaces and ensure the HA setup process completes quickly without exposure to untrusted networks; apply Cisco patches when available and monitor for unauthorized HA configuration attempts.
Cisco Prime Infrastructure 3.4.2+ or 3.5.1+; Cisco Evolved Programmable Network Manager 3.0.2+
- 1. Determine the current version of Cisco Prime Infrastructure (PI) or Evolved Programmable Network Manager (EPNM) by accessing the administration console
- 2. If running Prime Infrastructure: Plan upgrade to version 3.4.2 or later, or 3.5.1 or later (3.6 is affected - do not use 3.6)
- 3. If running EPNM: Plan upgrade to version 3.0.2 or later
- 4. Review Cisco upgrade documentation and release notes for the target version before initiating upgrade
- 5. Schedule maintenance window as upgrades require downtime
- 6. Perform full backup of the current system including database and configurations
- 7. Follow Cisco's documented upgrade procedure for the specific product and version
- 8. Verify the upgrade was successful and the new version is running
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Prime Infrastructure
Scoped from the published advisory
- 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-15958 — 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-15958 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