c-ares up to 1.17.0 ares_parse_soa_reply.c 1_16_1 buffer overflow

Summaryinfo

A vulnerability, which was classified as critical, has been found in c-ares up to 1.17.0. The impacted element is the function 1_16_1 of the file ares_parse_soa_reply.c. This manipulation causes buffer overflow. This vulnerability is registered as CVE-2020-22217. No exploit is available.

Detailsinfo

A vulnerability was found in c-ares up to 1.17.0. It has been declared as critical. Affected by this vulnerability is the function 1_16_1 of the file ares_parse_soa_reply.c. The manipulation with an unknown input leads to a buffer overflow vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Buffer overflow vulnerability in c-ares before 1_16_1 thru 1_17_0 via function ares_parse_soa_reply in ares_parse_soa_reply.c.

The weakness was published 08/23/2023 as 333. The advisory is shared at github.com. This vulnerability is known as CVE-2020-22217 since 08/13/2020. Technical details are known, but no exploit is available.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• c-ares

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17.0

Website

• Product: https://github.com/c-ares/c-ares/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion