# CVE-2020-24753: Memory corruption in n/a

> Attackers can execute code or cause crashes via crafted CBOR input due to uninitialized stack usage in the oocborrt library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 17 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x7rq-h6hf-g9vh

## What is CVE-2020-24753?

CVE-2020-24753 is a critical memory corruption vulnerability in n/a, published on 17 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A memory corruption vulnerability in Objective Open CBOR Run-time (oocborrt) in versions before 2020-08-12 could allow an attacker to execute code via crafted Concise Binary Object Representation (CBOR) input to the cbor2json decoder. An uncaught error while decoding CBOR Major Type 3 text strings leads to the use of an attacker-controllable uninitialized stack value. This can be used to modify memory, causing a crash or potentially exploitable heap corruption.

Weakness: CWE-908 (Use of Uninitialized Resource), CWE-787 (Out-of-bounds Write), CWE-755 (Improper Handling of Exceptional Conditions)

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

It affects 1 product.


Products: Objective Open Cbor Run-Time Project Objective Open Cbor Run-Time.

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

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

## Is CVE-2020-24753 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-24753 is a critical memory corruption vulnerability in n/a, published on 17 Sep 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-24753 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-24753/ (Markdown: https://insights.sbomify.com/CVE-2020-24753/index.md)
```

## Sources

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

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