# CVE-2018-0116: Auth bypass in Cisco Policy Suite

> Unauthenticated remote attackers can bypass RADIUS authentication in Cisco Policy Suite to gain subscriber access without a valid password.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2018
- **Updated:** 2 Dec 2024
- **Also known as:** GHSA-7cfm-96c5-jhrr

## What is CVE-2018-0116?

CVE-2018-0116 is a high-severity authentication bypass vulnerability in Cisco Policy Suite, published on 8 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-0116?

It affects 1 product.


Products: Cisco Mobility Services Engine.

## How do I fix CVE-2018-0116?

No fix has been published for CVE-2018-0116 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-0116 being exploited?

There is no known exploitation of CVE-2018-0116 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Policy Suite

- [CVE-2018-0374](https://insights.sbomify.com/CVE-2018-0374/): Missing authorization in Cisco Policy Suite unknown (critical 9.8)
- [CVE-2018-0375](https://insights.sbomify.com/CVE-2018-0375/): Hardcoded credentials in Cisco Policy Suite unknown (critical 9.8)
- [CVE-2018-0376](https://insights.sbomify.com/CVE-2018-0376/): Missing authorization in Cisco Policy Suite unknown (critical 9.8)
- [CVE-2018-0377](https://insights.sbomify.com/CVE-2018-0377/): Missing authorization in Cisco Policy Suite unknown (critical 9.8)
- [CVE-2015-4282](https://insights.sbomify.com/CVE-2015-4282/): Privilege escalation in n/a (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0116 and fix it if it is affected.

What it is: CVE-2018-0116 is a high-severity authentication bypass vulnerability in Cisco Policy Suite, published on 8 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-0116 in the wild and no public exploit code.

Affected product: Cisco Policy Suite. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-0116/ (Markdown: https://insights.sbomify.com/CVE-2018-0116/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-0116
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-0116
- OSV: https://osv.dev/vulnerability/CVE-2018-0116

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-0116/
Summaries are generated and may contain mistakes; the official description above is the record.