The c-ares function `ares_parse_naptr_reply()`, which is used for parsing NAPTR responses, could be triggered to read memory outside of the
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.3% (FIRST EPSS); higher than 88.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: nodejs (Alpine:v3.10) 6.11.1-r0; c-ares (Alpine:v3.3) 1.12.0-r1; nodejs (Alpine:v3.4) 6.7.0-r1.
Low priority for now. Upgrade to nodejs (Alpine:v3.10) 6.11.1-r0; c-ares (Alpine:v3.3) 1.12.0-r1; nodejs (Alpine:v3.4) 6.7.0-r1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
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 particular way.
- Published
- Jul 7, 2017
- Updated
- Jun 16, 2026
- EPSS
- 3.3% · 88th percentile
- CWE
- CWE-200
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| c-ares | c-ares | cpe:2.3:a:c-ares:c-ares |
| c-ares project | c-ares | cpe:2.3:a:c-ares_project:c-ares |
| nodejs | node.js | cpe:2.3:a:nodejs:node.js |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.js4.0.0 and later · up to 4.1.2 inclusive
- nodejs node.js4.2.0 and later · before 4.8.4
- nodejs node.js5.0.0 and later · up to 5.12.0 inclusive
- nodejs node.js6.0.0 and later · up to 6.8.1 inclusive
- nodejs node.js6.9.0 and later · before 6.11.1
- nodejs node.js7.0.0 and later · before 7.10.1
- nodejs node.js8.0.0 and later · before 8.1.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | nodejs | before 6.11.1-r0 | 6.11.1-r0 |
| Alpine:v3.3 | c-ares | before 1.12.0-r1 | 1.12.0-r1 |
| Alpine:v3.4 | nodejs | before 6.7.0-r1 | 6.7.0-r1 |
| Alpine:v3.5 | nodejs | before 6.9.5-r1 | 6.9.5-r1 |
| Alpine:v3.6 | nodejs | before 6.10.3-r1 | 6.10.3-r1 |
| Debian:12 | c-ares | before 1.12.0-4 | 1.12.0-4 |
| Debian:7 | c-ares | before 1.9.1-3+deb7u2 | 1.9.1-3+deb7u2 |
| openSUSE:Tumbleweed | c-ares | before 1.17.2-2.2 | 1.17.2-2.2 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs6-nodejs | before 0:6.11.3-2.el6 | 0:6.11.3-2.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs6-nodejs-debuginfo | before 0:6.11.3-2.el6 | 0:6.11.3-2.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs6-nodejs-devel | before 0:6.11.3-2.el6 | 0:6.11.3-2.el6 |
| Red Hat:rhel_software_collections:2::el6 | rh-nodejs6-nodejs-docs | before 0:6.11.3-2.el6 | 0:6.11.3-2.el6 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs6-nodejs | before 0:6.11.3-2.el7 | 0:6.11.3-2.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs6-nodejs-debuginfo | before 0:6.11.3-2.el7 | 0:6.11.3-2.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs6-nodejs-devel | before 0:6.11.3-2.el7 | 0:6.11.3-2.el7 |
| Red Hat:rhel_software_collections:2::el7 | rh-nodejs6-nodejs-docs | before 0:6.11.3-2.el7 | 0:6.11.3-2.el7 |
| SUSE:Linux Enterprise Desktop 12 SP2 | libcares2 | before 1.9.1-8.1 | 1.9.1-8.1 |
| SUSE:Linux Enterprise Module for Web and Scripting 12 | nodejs4 | before 4.8.4-15.5.1 | 4.8.4-15.5.1 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-atk | before 2.26.1-2.8.4 | 2.26.1-2.8.4 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-cairo | before 1.15.10-2.13.4 | 1.15.10-2.13.4 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-gdk-pixbuf | before 2.36.11-2.8.4 | 2.36.11-2.8.4 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-glib2 | before 2.54.3-2.14.7 | 2.54.3-2.14.7 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-gtk3 | before 3.10.9-2.15.3 | 3.10.9-2.15.3 |
| SUSE:Linux Enterprise Server 11 SP4-LTSS | firefox-harfbuzz | before 1.7.5-2.7.4 | 1.7.5-2.7.4 |
+9
Same product
c-ares: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-5180Heap-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 servic42Plan
- CVE-2025-31498c-ares has a use-after-free in read_answers()33Monitor
- CVE-2026-69184c-ares: CPU-exhaustion denial of service via unbounded DNS name compression pointer chains30Monitor
- CVE-2026-33630c-ares : Use-after-free / double-free in c-ares query-completion handling, remotely triggerable via ares_getaddrinfo() over TCP30Monitor
- CVE-2025-62408c-ares has a Use After Free vulnerability when connection is cleaned up after error23Monitor
- CVE-2020-22217Buffer 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.23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:c-ares | 1.12.0-r1 · Alpine:v3.3 | Package registry (OSV) |
| alpine:nodejs | 6.11.1-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:c-ares | 1.12.0-4 · Debian:12 | Package registry (OSV) |
| opensuse:c-ares | 1.17.2-2.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:rh-nodejs6-nodejs | 0:6.11.3-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs6-nodejs-debuginfo | 0:6.11.3-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs6-nodejs-devel | 0:6.11.3-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| red hat:rh-nodejs6-nodejs-docs | 0:6.11.3-2.el6 · Red Hat:rhel_software_collections:2::el6 | Package registry (OSV) |
| suse:firefox-atk | 2.26.1-2.8.4 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:firefox-cairo | 1.15.10-2.13.4 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:firefox-gdk-pixbuf | 2.36.11-2.8.4 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:firefox-glib2 | 2.54.3-2.14.7 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:firefox-gtk3 | 3.10.9-2.15.3 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:firefox-harfbuzz | 1.7.5-2.7.4 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:libcares2 | 1.9.1-8.1 · SUSE:Linux Enterprise Desktop 12 SP2 | Package registry (OSV) |
| suse:MozillaFirefox | 68.2.0-78.51.4 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:MozillaFirefox-branding-SLED | 68-21.9.8 · SUSE:Linux Enterprise Server 11 SP4-LTSS | Package registry (OSV) |
| suse:nodejs-common | 1.0-2.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
| suse:nodejs4 | 4.8.4-15.5.1 · SUSE:Linux Enterprise Module for Web and Scripting 12 | Package registry (OSV) |
| suse:nodejs6 | 6.11.1-11.5.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-200 · Exposure of Sensitive Information to an Unauthorized ActorCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.
The bug in code
The whole CWE-200 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
{ "permissions": ["tabs", "<all_urls>"], "background": { "service_worker": "analytics.js" }}Fixed
{ "permissions": ["activeTab"], "host_permissions": ["https://yildiz.example/*"]}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- ExcavationCAPEC-116likelihood: High · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- FootprintingCAPEC-169likelihood: High · Very Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- FingerprintingCAPEC-224likelihood: High · Very Low
- ICMP Echo Request PingCAPEC-285likelihood: Medium · Low
- TCP SYN ScanCAPEC-287Low
- Enumerate Mail Exchange (MX) RecordsCAPEC-290Low
ATT&CK techniques
- System Service DiscoveryT1007
- System Network Configuration DiscoveryT1016
- Remote System DiscoveryT1018
- System Owner/User DiscoveryT1033
- Masquerading: Match Legitimate Name or LocationT1036.005
- Network Service ScanningT1046
- System Network Connections DiscoveryT1049
- Process DiscoveryT1057
- Permission Groups DiscoveryT1069
- System Information DiscoveryT1082
- File and Directory DiscoveryT1083
- Account DiscoveryT1087
- Multi-Factor Authentication InterceptionT1111
- Peripheral Device DiscoveryT1120
- System Time DiscoveryT1124
- Access Token Manipulation:Token Impersonation/TheftT1134.001
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.