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

> A buffer overflow in the gilcc compiler allows attackers to cause a denial of service.

- **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:** No
- **Published:** 2 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h3pc-8hr5-v7p4

## What is CVE-2020-21572?

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

### Official description

Buffer overflow vulnerability in function src_parser_trans_stage_1_2_3 trgil gilcc before commit 803969389ca9c06237075a7f8eeb1a19e6651759, allows attackers to cause a denial of service.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Gilcc Project Gilcc.

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

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

## Is CVE-2020-21572 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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