dbcve.org
Policy SuiteApplication · Cisco

CVE-2018-0089

HIGH · 7.5 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 →
84/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
A vulnerability in the Policy and Charging Rules Function (PCRF) of the Cisco Policy Suite (CPS) could allow an unauthenticated, remote attacker to access sensitive data. The attacker could use this information to conduct additional reconnaissance attacks. The attacker would also have to have access to the internal VLAN where CPS is deployed. The vulnerability is due to incorrect permissions of certain system files and not sufficiently protecting sensitive data that is at rest. An attacker could exploit the vulnerability by using certain tools available on the internal network interface to request and view system files. An exploit could allow the attacker to find out sensitive information about the application. Cisco Bug IDs: CSCvf77666.

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

An information disclosure vulnerability in Cisco Policy Suite's PCRF component allows an unauthenticated attacker with internal VLAN access to view system files containing sensitive application data. The root cause is incorrect file permissions and insufficient protection of data at rest.

MitigationApply Cisco-provided patches for CSCvf77666, correct file permissions on system files, and implement encryption for sensitive data at rest. Restrict access to the internal VLAN as an additional defense layer.

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
Policy SuiteApplication
Affected:= 10.0.0= 11.0.0= 11.1.0

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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

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

  1. Identify installed Cisco Policy Suite version
    Access the system CLI or administrative interface and run: show version or check the package/install directory for the installed CPS version. Compare against affected versions: 10.0.0, 11.0.0, 11.1.0
    Affected if Installed version matches exactly 10.0.0, 11.0.0, or 11.1.0
  2. Confirm PCRF component is active
    Check if the PCRF (Policy and Charging Rules Function) component is running on the system. Use: show pcrf status or inspect running services/processes related to PCRF
    Affected if PCRF component is enabled and running on the affected CPS version
  3. Inspect system file permissions
    Review file permissions on system directories containing sensitive application data. Check files in /opt or system data directories. Look for world-readable or improperly permissioned files that should be restricted
    Affected if System files containing sensitive data have overly permissive access (world-readable or group-readable)
  4. Verify data-at-rest encryption status
    Check if encryption is enabled for sensitive data stored on the system. Review configuration files or database encryption settings. Look for unencrypted sensitive data files
    Affected if Sensitive application data is stored without encryption at rest
  5. Assess internal VLAN access exposure
    Determine if the system is accessible from internal VLANs by unauthorized users. Check network segmentation and VLAN access controls
    Affected if Unauthenticated users can access the system from internal VLANs

A system is affected if it runs Cisco Policy Suite version 10.0.0, 11.0.0, or 11.1.0 with the PCRF component enabled, and has incorrect file permissions or unencrypted sensitive data accessible from the internal VLAN.

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-provided patches for CSCvf77666, correct file permissions on system files, and implement encryption for sensitive data at rest. Restrict access to the internal VLAN as an additional defense layer.

Fix this in Policy Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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 locally
dbcve dependency scanner

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