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

> An out-of-bounds read in the Contiki uIP stack allows attackers to disclose sensitive memory contents via crafted IP packets.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** Yes
- **Published:** 11 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-13987, GHSA-g438-vfc9-cq65, RHBA-2021:4446, UBUNTU-CVE-2020-13987

## What is CVE-2020-13987?

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

### Official description

An issue was discovered in Contiki through 3.0. An Out-of-Bounds Read vulnerability exists in the uIP TCP/IP Stack component when calculating the checksums for IP packets in upper_layer_chksum in net/ipv4/uip.c.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `iscsi-initiator-utils` | Red Hat:enterprise_linux:8::baseos | All versions | 0:6.2.1.4-4.git095f59c.el8 |
| `iscsi-initiator-utils-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:6.2.1.4-4.git095f59c.el8 |
| `iscsi-initiator-utils-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:6.2.1.4-4.git095f59c.el8 |
| `iscsi-initiator-utils-iscsiuio` | Red Hat:enterprise_linux:8::baseos | All versions | 0:6.2.1.4-4.git095f59c.el8 |
| `iscsi-initiator-utils-iscsiuio-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:6.2.1.4-4.git095f59c.el8 |
| `python3-iscsi-initiator-utils` | Red Hat:enterprise_linux:8::baseos | All versions | 0:6.2.1.4-4.git095f59c.el8 |
| `python3-iscsi-initiator-utils-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:6.2.1.4-4.git095f59c.el8 |
| `iscsi-initiator-utils-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:6.2.1.4-4.git095f59c.el8 |
| `iscsi-initiator-utils-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:6.2.1.4-4.git095f59c.el8 |
| `iscsi-initiator-utils-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:6.2.1.4-4.git095f59c.el8 |
| `iscsi-initiator-utils-iscsiuio-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:6.2.1.4-4.git095f59c.el8 |
| `python3-iscsi-initiator-utils-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:6.2.1.4-4.git095f59c.el8 |

Products: Open-Iscsi Project Open-Iscsi, Siemens Sentron 3va Com100 Firmware, Siemens Sentron 3va Com800 Firmware, Siemens Sentron Pac3200 Firmware, Siemens Sentron Pac4200 Firmware, Uip Project Uip.

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

Apply the vendor's patch.

## Is CVE-2020-13987 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-17437](https://insights.sbomify.com/CVE-2020-17437/): Memory corruption in n/a (high 8.2)
- [CVE-2017-17840](https://insights.sbomify.com/CVE-2017-17840/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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