# CVE-2018-18960: Denial of service in n/a

> Attackers can exploit default SNMP v2c settings on Epson printers to launch amplification attacks, causing denial of service.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m8hg-ff53-qj52

## What is CVE-2018-18960?

CVE-2018-18960 is a medium-severity denial of service vulnerability in n/a, published on 24 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Epson WorkForce WF-2861 10.48 LQ22I3, 10.51.LQ20I6 and 10.52.LQ17IA devices. They use SNMP to find certain devices on the network, but the default version is v2c, allowing an amplification attack.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Epson Epson Workforce Wf-2861 Firmware.

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

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

## Is CVE-2018-18960 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-19248](https://insights.sbomify.com/CVE-2018-19248/): Missing authorization in n/a (critical 9.1)
- [CVE-2018-18959](https://insights.sbomify.com/CVE-2018-18959/): Denial of service in n/a (high 7.5)
- [CVE-2018-19232](https://insights.sbomify.com/CVE-2018-19232/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18960 is a medium-severity denial of service vulnerability in n/a, published on 24 Dec 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-18960 in the wild and no public exploit code.

Affected product: n/a. 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-18960/ (Markdown: https://insights.sbomify.com/CVE-2018-18960/index.md)
```

## Sources

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

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