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

> A global buffer overflow in N-Prolog allows attackers to execute arbitrary code or cause a denial of service via crafted input.

- **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:** 8 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-cc32-h3p6-f962

## What is CVE-2022-43343?

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

### Official description

N-Prolog v1.91 was discovered to contain a global buffer overflow vulnerability in the function gettoken() at Main.c.

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

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

It affects 1 product.


Products: N-Prolog Project N-Prolog.

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

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

## Is CVE-2022-43343 being exploited?

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

Public exploit code:

- Proof of concept for (CVE-2022-43343) (github_poc): https://github.com/Halcy0nic/CVE-2022-43343

## Fix prompt for AI coding agents

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

What it is: CVE-2022-43343 is a high-severity memory corruption vulnerability in n/a, published on 8 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43343 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-43343/ (Markdown: https://insights.sbomify.com/CVE-2022-43343/index.md)
```

## Sources

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

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