dbcve.org
Prime License ManagerApplication · Cisco

CVE-2018-15441

CRITICAL · 9.8 CVSS v3.0 Published 2018-11-28
Fix available
A fix is available. Upgrade to after 11.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 framework code of Cisco Prime License Manager (PLM) could allow an unauthenticated, remote attacker to execute arbitrary SQL queries. The vulnerability is due to a lack of proper validation of user-supplied input in SQL queries. An attacker could exploit this vulnerability by sending crafted HTTP POST requests that contain malicious SQL statements to an affected application. A successful exploit could allow the attacker to modify and delete arbitrary data in the PLM database or gain shell access with the privileges of the postgres user.

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 License Manager's web framework allows unauthenticated remote attackers to execute arbitrary SQL queries due to improper validation of user-supplied input in HTTP POST requests. Successful exploitation enables modification or deletion of arbitrary database data and potentially shell access with postgres user privileges.

MitigationApply Cisco's vendor patch for CVE-2018-15441 immediately; until patched, restrict network access to the PLM interface to minimize exposure.

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 License ManagerApplication
Affected:>= 11.0.1, <= 11.5= 11.5\(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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 checks

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

  1. Verify Cisco Prime License Manager is installed
    Check for the presence of Cisco Prime License Manager software on the system, typically installed under /opt or similar application directories. Look for the 'plist' command or related Cisco PLM components.
    Affected if The software is present on the system
  2. Determine the installed PLM version
    Locate and read the PLM version file or use the command 'sh version' within the PLM context, or check the about/overview page of the web interface. Compare the version number against the affected range: 11.0.1 through 11.5 (inclusive).
    Affected if The installed version is 11.0.1, 11.5, or any version between 11.0.1 and 11.5
  3. Confirm the PLM web service is running and accessible
    Check if the Cisco Prime License Manager web service (typically on port 443 or 8080) is listening and accessible on the network. Verify the service process is active using system process tools.
    Affected if The web interface is accessible from the network and responds to HTTP/HTTPS requests
  4. Check web framework configuration
    Examine the PLM web configuration files for any custom input validation settings. The vulnerability exists in the HTTP POST request handling of the web framework.
    Affected if The default web framework configuration is in use without additional input validation filters

The environment is affected if Cisco Prime License Manager version 11.0.1 through 11.5 is installed and its web interface is network-accessible, allowing unauthenticated SQL injection via HTTP POST requests.

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 a release after 11.5
Interim mitigation

Apply Cisco's vendor patch for CVE-2018-15441 immediately; until patched, restrict network access to the PLM interface to minimize exposure.

Fix this in Prime License Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-15441 — 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-2018-15441 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