VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

c-ares: vulnerability history, versions and safety

c-ares is a package in the OSS-Fuzz ecosystem. Vulert records 9 vulnerabilities for it across 4 affected ranges, from Jun 2020 to Sep 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded H3 M4 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all c-ares vulnerabilities

Vulert verdict on c-ares i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 28 Sep 2020. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 9 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 9 over 1 year · 0 in the last year i
  • Latest disclosure 28 Sep 2020 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from e0517f97d98845e2f56a43ba6ae2bbf339b5a3b0 up to 910df394fc40d90dda233b27bf122e50357943e6 (exclusive) 1
from 7d3591ee8a1a63e7748e68e6d880bd1763a32885 up to 5dd3629bc93449840c36dd635ea6cce606b8c366 (exclusive) 2
from f5b4c0851027286ef56b84a13c85424fe25c3703 up to 4d6975b3ec24aba44331d235bbcabf899be56cf2 (exclusive) 1
from 7d3591ee8a1a63e7748e68e6d880bd1763a32885 up to b949cc3ddfbeb1b3fba571fb53b186b645e66e9c (exclusive) 5

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 9

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 9 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for c-ares

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Use-of-uninitialized-value in c-ares: ares_parse_caa_reply N/A medium 4d6975b3ec24aba44331d235bbcabf899be56cf2 28 Sep 2020
Null-dereference READ Vulnerability in c-ares N/A unrated b949cc3ddfbeb1b3fba571fb53b186b645e66e9c 30 Jun 2020
Heap-buffer-overflow in c-ares: ares_parse_aaaa_reply N/A medium 5dd3629bc93449840c36dd635ea6cce606b8c366 01 Jul 2020
UNKNOWN WRITE Vulnerability in c-ares N/A high b949cc3ddfbeb1b3fba571fb53b186b645e66e9c 01 Jul 2020
Stack-buffer-overflow in ares_parse_aaaa_reply in c-ares N/A high b949cc3ddfbeb1b3fba571fb53b186b645e66e9c 01 Jul 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About c-ares

Is c-ares safe to use?

Vulert records 9 vulnerabilities for c-ares in OSS-Fuzz: 0 critical, 3 high, 4 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does c-ares have?

9 vulnerabilities are recorded for c-ares in the OSS-Fuzz ecosystem: 0 critical, 3 high, 4 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new c-ares vulnerabilities disclosed?

0 vulnerabilities were recorded for c-ares in the last 12 months, and the oldest entry in this database dates to 24 Jun 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of c-ares are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor c-ares for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the c-ares version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.