CVE-2018-0116
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 · uneditedA vulnerability in the RADIUS authentication module of Cisco Policy Suite could allow an unauthenticated, remote attacker to be authorized as a subscriber without providing a valid password; however, the attacker must provide a valid username. The vulnerability is due to incorrect RADIUS user credential validation. An attacker could exploit this vulnerability by attempting to access a Cisco Policy Suite domain configured with RADIUS authentication. An exploit could allow the attacker to be authorized as a subscriber without providing a valid password. This vulnerability affects the Cisco Policy Suite application running a release prior to 13.1.0 with Hotfix Patch 1 when RADIUS authentication is configured for a domain. Cisco Policy Suite Release 14.0.0 is also affected, as it includes vulnerable code, but RADIUS authentication is not officially supported in Cisco Policy Suite Releases 14.0.0 and later. Cisco Bug IDs: CSCvg40124.
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 confidenceCVE-2018-0116 is an authentication bypass vulnerability in Cisco Policy Suite's RADIUS authentication module that allows an unauthenticated remote attacker to be authorized as a subscriber using a valid username without providing a valid password, due to incorrect RADIUS user credential validation. The vulnerability is exploitable when RADIUS authentication is configured for a domain. Affected versions include releases prior to 13.1.0 with Hotfix Patch 1, and Release 14.0.0 which contains the vulnerable code but does not officially support RADIUS.
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= 13.0.0= 13.1.0= 14.0.0CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco Policy Suite installationLocate the Cisco Policy Suite or Cisco Mobility Services Engine installation and determine the software version using system inventory or version command (for example: show version, cps version, or consulting the installed packages)Affected if The installed version matches 13.0.0, 13.1.0, 14.0.0, or any release prior to 13.1.0 with Hotfix Patch 1
-
Confirm exact version numberQuery the installed software version using the appropriate command or configuration file for Cisco Policy Suite. Compare your version against the affected ranges: 13.0.0, 13.1.0, 14.0.0, or any version prior to 13.1.0 with Hotfix Patch 1Affected if The version is 13.0.0, 13.1.0, 14.0.0, or any version earlier than 13.1.0 with Hotfix Patch 1
-
Determine if RADIUS authentication is configured for any domainInspect the domain authentication configuration settings for Cisco Policy Suite. Look for RADIUS server configuration entries or authentication method settings that specify RADIUS for subscriber or domain authentication (typically found in the domain configuration, authentication profiles, or RADIUS client settings)Affected if RADIUS authentication is enabled and configured for one or more domains in the Cisco Policy Suite deployment
-
Verify RADIUS is actively in useReview the active authentication configuration to confirm RADIUS is the configured authentication method for subscriber authorization. Check domain-specific settings, authentication profiles, or RADIUS server bindings that indicate RADIUS is being used as the primary or fallback authentication mechanismAffected if RADIUS authentication is actively configured and available as an authentication option for subscriber or domain login
You are affected if you are running Cisco Policy Suite (or Cisco Mobility Services Engine) version 13.0.0, 13.1.0, 14.0.0, or any version prior to 13.1.0 with Hotfix Patch 1 AND RADIUS authentication is configured for a domain in your environment.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Cisco Policy Suite to Release 13.1.0 with Hotfix Patch 1 or later. For Release 14.0.0, disable RADIUS authentication if configured, as it is not an officially supported configuration.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0116 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-0116 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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