dbcve.org
Prime InfrastructureApplication · Cisco

CVE-2018-0097

MEDIUM · 6.1 CVSS v3.0 Published 2018-01-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 interface of Cisco Prime Infrastructure could allow an unauthenticated, remote attacker to redirect a user to a malicious web page, aka an Open Redirect. The vulnerability is due to improper input validation of the parameters in the HTTP request. An attacker could exploit this vulnerability by crafting an HTTP request that could cause the web application to redirect the request to a specific malicious URL. This vulnerability is known as an open redirect attack and is used in phishing attacks to get users to visit malicious sites without their knowledge. Cisco Bug IDs: CSCve37646.

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

Open redirect vulnerability in Cisco Prime Infrastructure web interface allows unauthenticated remote attackers to craft malicious HTTP requests with crafted redirect parameters that cause the application to forward users to attacker-controlled malicious websites, facilitating phishing attacks.

MitigationApply vendor patch from Cisco when available; meanwhile, implement URL validation/wafl rules to reject redirect parameters containing untrusted external domains, and educate users about risks of clicking untrusted links.

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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/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 if Cisco Prime Infrastructure is installed
    Check for the presence of Cisco Prime Infrastructure by reviewing installed applications, running services, or accessible web interfaces on common ports (ports 80, 443, 8080, 8443). Use system inventory tools or check for the service process 'Cisco Prime Infrastructure' in running services.
    Affected if Cisco Prime Infrastructure is found running in the environment
  2. Determine the installed version of Cisco Prime Infrastructure
    Access the web interface login page or check system files such as /opt/CSCOlumos/configuous_version or use CLI command 'show version' if administrative access is available. Compare the displayed version against the affected range.
    Affected if Any version of Cisco Prime Infrastructure is installed (all versions are affected)
  3. Verify the web interface is accessible and exposed
    Attempt to access the Cisco Prime Infrastructure login page via HTTP or HTTPS. Confirm the application responds to requests on the configured web ports.
    Affected if The web interface is reachable and responds to HTTP/HTTPS requests
  4. Check if redirect parameters are processed by the application
    Send a test HTTP request to the web interface with a crafted redirect parameter (such as ?url=http://example.com or ?next=http://example.com) and observe the HTTP response headers or body for evidence of external redirection.
    Affected if The application accepts and processes redirect parameters that can be controlled to point to external domains
  5. Review web server configuration for redirect handling
    Examine the web server configuration files (such as Apache httpd.conf, nginx.conf, or the embedded application server config) for patterns handling redirect, next, or destination parameters.
    Affected if The configuration allows arbitrary external URLs in redirect parameters without validation

If Cisco Prime Infrastructure is running and its web interface accepts redirect parameters without strict validation, the environment is affected by this open redirect vulnerability.

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 vendor patch from Cisco when available; meanwhile, implement URL validation/wafl rules to reject redirect parameters containing untrusted external domains, and educate users about risks of clicking untrusted links.

Fix this in Prime Infrastructure Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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