N-Prolog 1.91 Main.c gettoken buffer overflow

Summaryinfo

A vulnerability classified as critical has been found in N-Prolog 1.91. This issue affects the function gettoken of the file Main.c. The manipulation leads to buffer overflow. This vulnerability is uniquely identified as CVE-2022-43343. No exploit exists.

Detailsinfo

A vulnerability was found in N-Prolog 1.91 and classified as critical. This issue affects the function gettoken of the file Main.c. The manipulation with an unknown input leads to a buffer overflow vulnerability. Using CWE to declare the problem leads to CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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

The weakness was disclosed 11/08/2022 as 75. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2022-43343 since 10/17/2022. Technical details of the vulnerability are known, but there is no available exploit.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• N-Prolog

Version

• 1.91

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion