dbcve.org
Prime InfrastructureApplication · Cisco

CVE-2014-2152

MEDIUM · 6.8 CVSS v2.0 Published 2015-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
Cross-site request forgery (CSRF) vulnerability in the INSERT page in Cisco Prime Infrastructure (PI) allows remote attackers to hijack the authentication of arbitrary users, aka Bug ID CSCun21868.

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 · moderate confidence

Cross-site request forgery (CSRF) vulnerability in Cisco Prime Infrastructure's INSERT page allows remote attackers to hijack user authentication by tricking authenticated users into unknowingly submitting malicious requests. The attack exploits the lack of proper request validation, allowing attackers to perform unauthorized actions on behalf of legitimate users.

MitigationImplement anti-CSRF tokens on all state-changing operations including the INSERT page, validate Referer headers, and apply SameSite cookie attributes. Contact Cisco for available patches for this vulnerability.

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:all versions

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 installation
    Check if Cisco Prime Infrastructure is running by accessing the web interface or checking running services. Determine the installed version by logging into the admin console and viewing the version information typically found in Help > About or the system dashboard.
    Affected if The product is Cisco Prime Infrastructure and the version cannot be determined or falls within all released versions.
  2. Locate the INSERT page endpoint
    Access the INSERT functionality within Cisco Prime Infrastructure. The INSERT page is typically found under the administration or configuration sections where new entries can be added. Inspect the HTML source of this page to examine form elements.
    Affected if The INSERT page exists and is accessible without requiring re-authentication for each request.
  3. Inspect for anti-CSRF tokens
    View the HTML source of the INSERT page and search for hidden form fields containing tokens (such as csrf_token, csrfKey, or similar). Check if these tokens are required for form submission and are validated server-side.
    Affected if No anti-CSRF token is present in the INSERT page forms, or tokens are not validated on submission.
  4. Check Referer header validation
    Submit a request to the INSERT page with a modified or missing Referer header using a tool like Burp Suite or curl. Observe whether the request is accepted or rejected based on the Referer origin.
    Affected if The application accepts requests without validating the Referer header or accepts requests from arbitrary origins.
  5. Verify SameSite cookie attributes
    Capture HTTP responses from the INSERT page using browser developer tools or a proxy. Examine the Set-Cookie headers for the SameSite attribute on session cookies.
    Affected if Session cookies do not have the SameSite attribute set, or SameSite is set to None without Secure flags.

A user is affected if Cisco Prime Infrastructure is running and the INSERT page lacks anti-CSRF token validation, does not validate Referer headers, and does not use SameSite cookie attributes.

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

Implement anti-CSRF tokens on all state-changing operations including the INSERT page, validate Referer headers, and apply SameSite cookie attributes. Contact Cisco for available patches for this vulnerability.

Fix this in Prime Infrastructure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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