# CVE-2022-44321: Memory corruption in n/a

> A heap buffer overflow in PicoC allows attackers to execute arbitrary code or cause denial of service via crafted input.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-ccfq-vqq6-835v

## What is CVE-2022-44321?

CVE-2022-44321 is a medium-severity memory corruption vulnerability in n/a, published on 8 Nov 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

PicoC Version 3.2.2 was discovered to contain a heap buffer overflow in the LexSkipComment function in lex.c when called from LexScanGetToken.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-44321?

It affects 1 product.


Products: Picoc Project Picoc.

## How do I fix CVE-2022-44321?

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

## Is CVE-2022-44321 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-44321 exists.

## Other vulnerabilities in n/a

- [CVE-2019-16277](https://insights.sbomify.com/CVE-2019-16277/): Memory corruption in n/a (high 7.8)
- [CVE-2022-44312](https://insights.sbomify.com/CVE-2022-44312/): Memory corruption in n/a (medium 5.5)
- [CVE-2022-44313](https://insights.sbomify.com/CVE-2022-44313/): Memory corruption in n/a (medium 5.5)
- [CVE-2022-44314](https://insights.sbomify.com/CVE-2022-44314/): Memory corruption in n/a (medium 5.5)
- [CVE-2022-44315](https://insights.sbomify.com/CVE-2022-44315/): Memory corruption in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-44321 and fix it if it is affected.

What it is: CVE-2022-44321 is a medium-severity memory corruption vulnerability in n/a, published on 8 Nov 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-44321 exists.

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-2022-44321/ (Markdown: https://insights.sbomify.com/CVE-2022-44321/index.md)
```

## Sources

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

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