# CVE-2013-4807: Other in n/a

> Remote attackers can modify data on specific HP LaserJet printers via unspecified vectors, requiring firmware updates.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:C/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hw48-wq5r-qc92

## What is CVE-2013-4807?

CVE-2013-4807 is a high-severity vulnerability in n/a, published on 4 Aug 2013. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability on the HP LaserJet Pro P1102w, P1606dn, M1212nf MFP, M1213nf MFP, M1214nfh MFP, M1216nfh MFP, M1217nfw MFP, M1218nfs MFP, and CP1025nw with firmware before 2013-07-26 20130703 allows remote attackers to modify data via unknown vectors.

## Which versions are affected by CVE-2013-4807?

It affects 9 products.


Products: Hp Hotspot Laserjet Pro M1218nfs Mfp Firmware, Hp Laserjet Pro Cp1025nw Firmware, Hp Laserjet Pro M1212nf Mfp Firmware, Hp Laserjet Pro M1213nf Mfp Firmware, Hp Laserjet Pro M1214nfh Mfp Firmware, Hp Laserjet Pro M1216nfh Multifunction Printer Firmware, Hp Laserjet Pro M1217nfw Multifunction Printer Firmware, Hp Laserjet Pro P1102w Firmware, Hp Laserjet Pro P1606dn Firmware.

## How do I fix CVE-2013-4807?

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

## Is CVE-2013-4807 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4807 and fix it if it is affected.

What it is: CVE-2013-4807 is a high-severity vulnerability in n/a, published on 4 Aug 2013. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4807 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-2013-4807/ (Markdown: https://insights.sbomify.com/CVE-2013-4807/index.md)
```

## Sources

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

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