LiveActive security incident?Get immediate response
CVE Record

CVE-2020-14354: A possible use-after-free and double-free in c-ares lib version 1.16.0 if ares_destroy() is called prior to...

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. This flaw possibly allows an attacker to crash the service that uses c-ares lib. The highest threat from this vulnerability is to this service availability.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-14354 is a memory-management flaw in c-ares, a DNS resolver library. If an application destroys a c-ares channel before ares_getaddrinfo() finishes, the library may use or free already-freed memory. The cited impact is service crash, so business risk is interruption of applications that depend on affected c-ares builds.

Executive priority

Treat this as a service-availability risk, not a confirmed widespread emergency. Patch during the next normal security maintenance window, faster for critical services using c-ares. The inconsistent affected-version evidence means vulnerability managers should verify vendor package status before declaring closure.

Technical view

The issue is described as possible use-after-free and double-free behavior around ares_destroy() and incomplete ares_getaddrinfo() work. The source bundle identifies availability as the highest threat. No CVSS score is provided. The affected-version evidence is inconsistent: the description names 1.16.0, while the affected array lists 1.16.1.

Likely exposure

Exposure is most likely in software that links c-ares and uses asynchronous ares_getaddrinfo(). Inventory should include OS packages, containers, static builds, and vendor-bundled libcares copies. Because the source bundle conflicts on the affected version, teams should verify exposure against their distributor or upstream c-ares guidance.

Exploitation context

The bundle does not show KEV listing and does not cite active exploitation. The stated consequence is service crash, not confirmed code execution. Public references include a Packet Storm item, so disclosure is public, but the provided evidence is not enough to claim attacks in the wild.

Researcher notes

The CVE record describes c-ares 1.16.0, while the provided affected array lists c-ares 1.16.1. CVSS is absent and CWE-120 does not fully describe the free-lifecycle issue. Confidence is medium because impact is clear, but affected-version boundaries and fixed-release details require vendor confirmation.

Mitigation direction

  • Follow c-ares and OS vendor advisories; update to a vendor-fixed package or upstream fixed release.
  • Prioritize customer-facing or internet-reachable services that depend on c-ares DNS resolution.
  • Restart rebuilt services and containers so they load the corrected library.
  • Monitor affected services for resolver-related crashes until remediation is complete.
  • If immediate patching is blocked, reduce exposure and ensure rapid service restart controls.

Validation and detection

  • Inventory c-ares versions in OS packages, containers, static builds, and vendor appliances.
  • Confirm deployed builds against the source-bundle version evidence and vendor fixed-package guidance.
  • Review application code for asynchronous ares_getaddrinfo use with possible early cleanup.
  • Check crash logs for resolver timing, double-free, or use-after-free indicators.
  • After updates, rerun service health checks and DNS resolution regression tests.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-14354 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/ac-aresc-ares 1.16.1Listed
Weakness

CWE details

CWE-120

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs