# CVE-2020-16849: Information disclosure in n/a

> An unauthenticated network attacker can exploit an improper length parameter handling flaw in the IPv4/ICMPv4 component to expose sensitive information.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 30 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m3wc-g5cv-5v98

## What is CVE-2020-16849?

CVE-2020-16849 is a high-severity vulnerability in n/a, published on 30 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Canon MF237w 06.07 devices. An "Improper Handling of Length Parameter Inconsistency" issue in the IPv4/ICMPv4 component, when handling a packet sent by an unauthenticated network attacker, may expose Sensitive Information.

## Which versions are affected by CVE-2020-16849?

It affects 28 products.


Products: Canon Ir2202n Firmware, Canon Ir2204f Firmware, Canon Ir2204n Firmware, Canon Ir2206if Firmware, Canon Ir2206n Firmware, Canon Lbp113w Firmware, Canon Lbp151dw Firmware, Canon Lbp162dw Firmware, Canon Mf113w Firmware, Canon Mf212w Firmware, Canon Mf216n Firmware, Canon Mf217w Firmware, Canon Mf226dn Firmware, Canon Mf229dw Firmware, Canon Mf231 Firmware, Canon Mf232w Firmware, Canon Mf237w Firmware, Canon Mf244dw Firmware, Canon Mf247dw Firmware, Canon Mf249dw Firmware and 8 more.

## How do I fix CVE-2020-16849?

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

## Is CVE-2020-16849 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-16849 and fix it if it is affected.

What it is: CVE-2020-16849 is a high-severity vulnerability in n/a, published on 30 Nov 2020. 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-2020-16849 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-2020-16849/ (Markdown: https://insights.sbomify.com/CVE-2020-16849/index.md)
```

## Sources

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

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