C-Ares vulnerabilitiesNone on the known-exploited list.
C-Ares has 5 published vulnerabilities across 1 product in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is C-Ares, with 5. If you run C-Ares software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which C-Ares products have the most vulnerabilities?
C-Ares leads with 5 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which C-Ares vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of C-Ares's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which C-Ares flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 8.6%CVE-2016-5180Critical
Heap-based buffer overflow in the ares_create_query function in c-ares 1.x before 1.12.0 allows remote attackers to cause a denial of service (out-of-bounds write) or possibly execute arbitrary code via a hostname...
- 3.3%CVE-2017-1000381High
The c-ares function `ares_parse_naptr_reply()`, which is used for parsing NAPTR responses, could be triggered to read memory outside of the given input buffer if the passed in DNS response packet was crafted in a...
- 1.0%CVE-2020-22217Medium
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.
- 0.5%
A possible use-after-free and double-free in c-ares lib version 1.16.0 if ares_destroy() is called prior to ares_getaddrinfo() completing.
- 0.4%CVE-2024-25629Medium
c-ares is a C library for asynchronous DNS requests.
All C-Ares products we track.
1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running C-Ares? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Heap-based buffer overflow in the ares_create_query function in c-ares 1.x before 1.12.0 allows remote attackers to cause a denial of service (out-of-bounds write) or possibly execute arbitrary code via a hostname with an escaped trailing dot.
- Matched to
- C-Ares on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 5 published vulnerabilities across 1 product and 66 versions from C-Ares.
None of C-Ares's vulnerabilities is on the list of flaws known to be exploited today.
C-Ares, with 5 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the C-Ares products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.