Evolved Programmable Network ManagerApplication · Cisco
CVE-2023-20271
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 and Cisco Evolved Programmable Network Manager (EPNM) could allow an authenticated, remote attacker to conduct SQL injection attacks on an affected system. This vulnerability is due to improper validation of user-submitted parameters. An attacker could exploit this vulnerability by authenticating to the application and sending malicious requests to an affected system. A successful exploit could allow the attacker to obtain and modify sensitive information that is stored in the underlying database.
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 confidenceSQL injection vulnerability in Cisco Prime Infrastructure and Cisco EPNM web-based management interfaces due to improper validation of user-supplied parameters. An authenticated attacker can inject malicious SQL queries via the web interface to read or modify sensitive data stored in the underlying database.
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
< 7.1.1
Prime InfrastructureApplication
< 3.10.4= 3.10.4CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Cisco productAccess the web interface login page or check system documentation to determine if you are running Cisco Prime Infrastructure or Cisco Evolved Programmable Network Manager (EPNM). Look at the product name displayed on the login page or in the admin console.Affected if The product is Cisco Prime Infrastructure or Cisco EPNM.
-
Determine product version numberLog into the web-based management interface and navigate to the About or Administration section to find the exact version number. Alternatively, check the version displayed on the login page or in the software release notes.Affected if The installed version is Cisco EPNM < 7.1.1, or Cisco Prime Infrastructure = 3.10.4 or < 3.10.4.
-
Verify web management interface is accessibleAttempt to access the web-based management interface URL (typically HTTPS on port 443 or 8443) from a browser or using a tool like curl to confirm the interface is reachable and responding.Affected if The web interface is exposed and accepts connections.
-
Confirm authentication is configuredCheck whether valid administrator credentials exist for the web interface and whether the interface permits authenticated user sessions.Affected if Valid credentials can be used to log into the web interface, as authentication is required for exploitation.
You are affected if you are running Cisco EPNM below version 7.1.1 or Cisco Prime Infrastructure version 3.10.4 or lower, and the web-based management interface is accessible with valid credentials.
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.10.47.1.1
Apply Cisco's official patches for affected versions. As an interim control, restrict web management interface access to trusted IP addresses and implement strict input validation on the application layer.
Cisco Prime Infrastructure: 3.10.5 or later | Cisco Evolved Programmable Network Manager: 7.1.1 or later
- 1. Back up the current Cisco Prime Infrastructure or Evolved Programmable Network Manager configuration and database.
- 2. Schedule a maintenance window for the upgrade to minimize business impact.
- 3. For Prime Infrastructure: Upgrade to version 3.10.5 or later.
- 4. For Evolved Programmable Network Manager: Upgrade to version 7.1.1 or later.
- 5. After upgrade, verify the web-based management interface is accessible and functioning normally.
- 6. Confirm the SQL injection vulnerability is remediated by testing that properly validated input is accepted and malicious SQL syntax in parameters is rejected.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Evolved Programmable Network Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20271 — 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-2023-20271 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