CVE-2019-1822
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 web-based management interface of Cisco Prime Infrastructure (PI) and Cisco Evolved Programmable Network (EPN) Manager could allow an authenticated, remote attacker to execute code with root-level privileges on the underlying operating system. This vulnerability exist because the software improperly validates user-supplied input. An attacker could exploit this vulnerability by uploading a malicious file to the administrative web interface. A successful exploit could allow the attacker to execute code with root-level privileges on the underlying operating 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 confidenceThis is an authenticated remote code execution vulnerability in Cisco Prime Infrastructure and EPN Manager's web-based management interface. The vulnerability stems from improper validation of user-supplied input during file upload, allowing an authenticated attacker to upload a malicious file and execute arbitrary code with root-level privileges on the underlying operating system.
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< 3.0.1< 3.4.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 installed Cisco productAccess the web management interface and check the version information, typically found in Help > About or the login page footer. Alternatively, check the system using CLI: 'show version' or look for installation directories like /opt/CSCOlumos or /opt/primeinfraAffected if The product is Cisco Evolved Programmable Network Manager or Cisco Prime Infrastructure
-
Determine exact version numberIn the web interface, navigate to Administration > Settings > Software Updates or Help > About to view the precise version build. In CLI, run 'show version' or check /opt/CSCOlumos/version.txt for EPN ManagerAffected if Version is below 3.0.1 for EPN Manager or below 3.4.1 for Prime Infrastructure
-
Verify web management interface is accessibleConfirm the web-based management interface (HTTPS on port 443 or 8080) is reachable from network. Check if the interface is exposed to untrusted networksAffected if The web interface is accessible to unauthenticated or untrusted network segments
-
Review authentication controlsCheck that strong authentication is required for web interface access. Verify user accounts and privilege levels in Administration > User Management or equivalentAffected if The interface permits authentication with low-privilege accounts or uses default credentials
-
Inspect for unauthorized file uploadsCheck server filesystem for unexpected files in web-accessible directories such as /tftpboot, /tmp, or upload staging directories. Review web server logs for suspicious POST requests to file upload endpointsAffected if Unexpected files exist or unusual upload activity is logged in web server access logs
Your environment is affected if you run EPN Manager below 3.0.1 or Prime Infrastructure below 3.4.1 and the web management interface is accessible to authenticated attackers.
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 data3.0.13.4.1
Apply the vendor-supplied patches for CVE-2019-1822. Until patches are available, restrict administrative web interface access to trusted users only and monitor for suspicious file upload activities.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1822 — 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-1822 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