CVE-2016-5180
A public proof of concept exists; no exploitation attested.
- Published2016-10-03
- WeaknessCWE-787
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2016-10-0315:59CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-5180?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-5180?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.0 | = 1.0.0 | no fix published | NVD |
| 1.1 | = 1.1.0 | no fix published | NVD |
| 1.2 | = 1.2.0 | no fix published | NVD |
| 1.2 | = 1.2.1 | no fix published | NVD |
| 1.3 | = 1.3.0 | no fix published | NVD |
| 1.3 | = 1.3.1 | no fix published | NVD |
| 1.3 | = 1.3.2 | no fix published | NVD |
| 1.4 | = 1.4.0 | no fix published | NVD |
| 1.5 | = 1.5.0 | no fix published | NVD |
| 1.5 | = 1.5.1 | no fix published | NVD |
| 1.5 | = 1.5.2 | no fix published | NVD |
| 1.5 | = 1.5.3 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 12.4 | = 12.04 | no fix published | NVD |
| 14.4 | = 14.04 | no fix published | NVD |
| 16.4 | = 16.04 | no fix published | NVD |
| 16.10 | = 16.10 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.x | ≥ 4.0.0, < 4.6.1 | 4.6.1 | NVD |
| 0.12 | ≥ 0.12.0, < 0.12.17 | 0.12.17 | NVD |
| 0.10 | ≥ 0.10.0, < 0.10.48 | 0.10.48 | NVD |
2 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
No fix published by the sources we read yet. NVD record
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 3 repositories, unverifiedpouriam23/CVE-2016-5180pouriam23/CVE-2016-5180-docker-pouriam23/final-CVE-2016-5180 PoC-in-GitHub
Sources
- NVDCVSS 3.19.8read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- NVDweakness (CWE)CWE-787read 2026-10-23
- FIRST EPSSEPSS score8.6 %2026-10-22
- PoC-in-GitHubproof of concept3read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2016-10-03
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2016-5180?
Is CVE-2016-5180 actively exploited?
What is the CVSS score for CVE-2016-5180?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.