dbcve.org
Prime InfrastructureApplication · Cisco

CVE-2017-6698

MEDIUM · 5.4 CVSS v3.0 Published 2017-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 Cisco Prime Infrastructure (PI) and Evolved Programmable Network Manager (EPNM) SQL database interface could allow an authenticated, remote attacker to impact the confidentiality and integrity of the application by executing arbitrary SQL queries, aka SQL Injection. More Information: CSCvc23892 CSCvc35270 CSCvc35626 CSCvc35630 CSCvc49568. Known Affected Releases: 3.1(1) 2.0(4.0.45B).

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 the SQL database interface of Cisco Prime Infrastructure (PI) and Evolved Programmable Network Manager (EPNM) allows an authenticated remote attacker to execute arbitrary SQL queries, compromising application confidentiality and integrity.

MitigationApply Cisco security patches for the identified affected releases (3.1(1), 2.0(4.0.45B)) per Cisco advisory CSCvc23892. If patches are unavailable, restrict network access to the management interface to trusted IPs and enforce least-privilege user accounts.

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
Affected:= 2.0\(4.0.45b\)= 3.1\(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
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 Cisco Prime Infrastructure version
    Log into the Prime Infrastructure web interface and navigate to Admin > Software Updates > Updates, or use the CLI command 'show version' to determine the installed software version
    Affected if The installed version matches exactly 2.0(4.0.45b) or 3.1(1)
  2. Identify EPNM version
    Log into the EPNM interface and check the version through the administration menu or CLI command 'show version'
    Affected if EPNM is installed and running any version within the affected product line (note: specific EPNM versions were not enumerated in the CVE but the product is listed as affected)
  3. Verify management interface accessibility
    Determine if the Cisco PI/EPNM management interface (HTTPS web portal) is accessible from untrusted networks by reviewing firewall rules, ACLs, or network perimeter configurations
    Affected if The management interface is exposed to networks outside the trusted administrative zone
  4. Review user authentication configuration
    Check the local user accounts configured in Prime Infrastructure under Users > User Management, or via CLI 'show running-config | include user' to enumerate accounts with database query privileges
    Affected if Multiple user accounts exist with elevated privileges or the default admin account remains in use
  5. Confirm SQL database interface is enabled
    Verify whether the SQL database interface feature is enabled by checking the application configuration or reviewing if database query functionalities are accessible to authenticated users
    Affected if The SQL database interface feature is accessible to authenticated users without additional access controls

The environment is affected if running Cisco Prime Infrastructure version 2.0(4.0.45b) or 3.1(1), or EPNM, with the management interface network-accessible and authenticated user accounts able to access the SQL database interface.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco security patches for the identified affected releases (3.1(1), 2.0(4.0.45B)) per Cisco advisory CSCvc23892. If patches are unavailable, restrict network access to the management interface to trusted IPs and enforce least-privilege user accounts.

Fix this in Prime Infrastructure Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6698 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2017-6698 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