CVE-2022-43343: N-Prolog v1.91 was discovered to contain a global buffer overflow vulnerability in the function gettoken() at
CVE-2022-43343 is a high-severity flaw (CVSS 7.5) affecting n-prolog. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
N-Prolog v1.91 was discovered to contain a global buffer overflow vulnerability in the function gettoken() at Main.c.
Why this priority
- High severity
- Public exploit reference
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.2% (top 33%) |
| CISA exploited list | No |
| Weakness | CWE-120 |
| Published | 2022-11-08 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-43343?
n-prolog: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2022-43343 being exploited?
CVE-2022-43343 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-43343 affect?
CVE-2022-43343 affects n-prolog. Severity is high (CVSS 7.5). N-Prolog v1.91 was discovered to contain a global buffer overflow vulnerability in the function gettoken() at Main.c.
How urgent is CVE-2022-43343?
Priority 53/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action