# CVE-2018-15437: Cisco Immunet and Cisco AMP for Endpoints System Scan Denial of Service Vulnerability

> A local attacker can disable system scanning in Cisco AMP for Endpoints, allowing malicious executables to run without analysis.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Nov 2018
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-f582-5356-9mc6

## What is CVE-2018-15437?

CVE-2018-15437 is a medium-severity denial of service vulnerability in Cisco AMP for Endpoints, published on 8 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the system scanning component of Cisco Immunet and Cisco Advanced Malware Protection (AMP) for Endpoints running on Microsoft Windows could allow a local attacker to disable the scanning functionality of the product. This could allow executable files to be launched on the system without being analyzed for threats. The vulnerability is due to improper process resource handling. An attacker could exploit this vulnerability by gaining local access to a system running Microsoft Windows and protected by Cisco Immunet or Cisco AMP for Endpoints and executing a malicious file. A successful exploit could allow the attacker to prevent the scanning services from functioning properly and ultimately prevent the system from being protected from further intrusion.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 2 products.


Products: Cisco Advanced Malware Protection for Endpoints, Cisco Immunet for Endpoints.

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

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

## Is CVE-2018-15437 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-15437 exists.

Public exploit code:

- Cisco Immunet < 6.2.0 / Cisco AMP For Endpoints 6.2.0 - Denial of Service (exploitdb)

## Other vulnerabilities in Cisco AMP for Endpoints

- [CVE-2021-1280](https://insights.sbomify.com/CVE-2021-1280/): Cisco Advanced Malware Protection for Endpoints and Immunet for Windows DLL Hijacking Vulnerability (high 7.8)
- [CVE-2021-1386](https://insights.sbomify.com/CVE-2021-1386/): Path traversal in Cisco AMP for Endpoints (high 7.0)
- [CVE-2019-1932](https://insights.sbomify.com/CVE-2019-1932/): Cisco Advanced Malware Protection for Endpoints Windows Command Injection Vulnerability (medium 6.7)
- [CVE-2017-12312](https://insights.sbomify.com/CVE-2017-12312/): Path traversal in Cisco Immunet Antimalware Installer (medium 6.7)
- [CVE-2020-3314](https://insights.sbomify.com/CVE-2020-3314/): Cisco AMP for Endpoints Mac Connector Software File Scan Denial of Service Vulnerability (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-15437 is a medium-severity denial of service vulnerability in Cisco AMP for Endpoints, published on 8 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-15437 exists.

Affected product: Cisco AMP for Endpoints. 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-15437/ (Markdown: https://insights.sbomify.com/CVE-2018-15437/index.md)
```

## Sources

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

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