Evolved Programmable Network ManagerApplication · Cisco

CVE-2019-1824

HIGH · 8.1 CVSS v3.0 Published 2019-05-16
Fix available
A fix is available. Upgrade to 3.0.1 / 3.4.1 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
A 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 arbitrary SQL queries. This vulnerability exist because the software improperly validates user-supplied input in SQL queries. An attacker could exploit this vulnerability by sending a crafted HTTP request that contains malicious SQL statements to the affected application. A successful exploit could allow the attacker to view or modify entries in some database tables, affecting the integrity of the data.

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 confidence

SQL injection vulnerability in Cisco Prime Infrastructure and EPN Manager web-based management interface allows authenticated remote attackers to execute arbitrary SQL queries through malicious SQL statements in crafted HTTP requests due to improper input validation.

MitigationApply the vendor-provided patch or upgrade to a fixed Cisco Prime Infrastructure/EPN Manager version that properly validates and sanitizes user input in SQL queries.

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
Evolved Programmable Network ManagerApplication
Affected:< 3.0.1
Prime InfrastructureApplication
Affected:< 3.4.1

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Cisco management product
    Check system for Cisco Prime Infrastructure or Evolved Programmable Network Manager installations. Common locations include /opt/cisco/ or check for running processes like 'prime' or 'epn' services.
    Affected if Either Cisco Prime Infrastructure or Cisco EPN Manager is installed
  2. Determine installed version
    For Prime Infrastructure, typically check the /opt/csmp/VERSION file or use CLI: show version. For EPN Manager, check /opt/epnm/VERSION or use: show software version.
    Affected if Version is below 3.4.1 for Prime Infrastructure or below 3.0.1 for EPN Manager
  3. Verify web management interface is accessible
    Confirm the web-based management interface (HTTPS on ports 443, 8080, or 8443) is reachable and responds to requests.
    Affected if Web interface is exposed and responds to authentication requests
  4. Check for unauthorized SQL injection indicators
    Review web server access logs and application logs for unusual SQL syntax in HTTP request parameters, such as quotes, UNION statements, or SQL keywords in query strings.
    Affected if Logs show SQL-like characters or keywords (', UNION, SELECT, DROP) in request parameters

User is affected if Cisco Prime Infrastructure below 3.4.1 or EPN Manager below 3.0.1 is installed and the web-based management interface is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 3.0.1 / 3.4.1 or later
Fixed in 3.0.13.4.1
Interim mitigation

Apply the vendor-provided patch or upgrade to a fixed Cisco Prime Infrastructure/EPN Manager version that properly validates and sanitizes user input in SQL queries.

Fix this in Evolved Programmable Network Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1824 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1824 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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