The getaddrinfo function in glibc before 2.15, when compiled with libidn and the AI_IDN flag is used, allows context-dependent attackers to
Noroxi assessment
Priority: Monitor (action score 21/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: 2.6% (FIRST EPSS); higher than 85.6% of all records.
- Special conditions such as timing or configuration are required.
- Fixed version: glibc (Debian:12) 2.15-1; eglibc (Debian:6.0) 2.11.3-4+deb6u5; eglibc (Debian:7) 2.13-38+deb7u8.
Low priority for now. Upgrade to glibc (Debian:12) 2.15-1; eglibc (Debian:6.0) 2.11.3-4+deb6u5; eglibc (Debian:7) 2.13-38+deb7u8 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
Primary sources: NVD · CVE.org · FIRST EPSS
The getaddrinfo function in glibc before 2.15, when compiled with libidn and the AI_IDN flag is used, allows context-dependent attackers to cause a denial of service (invalid free) and possibly execute arbitrary code via unspecified vectors, as demonstrated by an internationalized domain name to ping6.
- Published
- Aug 26, 2015
- Updated
- Jun 16, 2026
- EPSS
- 2.6% · 85th percentile
- CWE
- CWE-17
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.6%
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 |
|---|---|---|
| gnu | glibc | cpe:2.3:a:gnu:glibc |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gnu glibcup to 2.14.1 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | glibc | before 2.15-1 | 2.15-1 |
| Debian:6.0 | eglibc | before 2.11.3-4+deb6u5 | 2.11.3-4+deb6u5 |
| Debian:7 | eglibc | before 2.13-38+deb7u8 | 2.13-38+deb7u8 |
| Red Hat:enterprise_linux:5::client | glibc | before 0:2.5-123.el5_11.3 | 0:2.5-123.el5_11.3 |
| Red Hat:enterprise_linux:5::client | glibc-common | before 0:2.5-123.el5_11.3 | 0:2.5-123.el5_11.3 |
| Red Hat:enterprise_linux:5::client | glibc-debuginfo | before 0:2.5-123.el5_11.3 | 0:2.5-123.el5_11.3 |
| Red Hat:enterprise_linux:5::client | glibc-debuginfo-common | before 0:2.5-123.el5_11.3 | 0:2.5-123.el5_11.3 |
| Red Hat:enterprise_linux:5::client | glibc-devel | before 0:2.5-123.el5_11.3 | 0:2.5-123.el5_11.3 |
| Red Hat:enterprise_linux:5::client | glibc-headers | before 0:2.5-123.el5_11.3 | 0:2.5-123.el5_11.3 |
| Red Hat:enterprise_linux:5::client | glibc-utils | before 0:2.5-123.el5_11.3 | 0:2.5-123.el5_11.3 |
| Red Hat:enterprise_linux:5::client | nscd | before 0:2.5-123.el5_11.3 | 0:2.5-123.el5_11.3 |
| Red Hat:enterprise_linux:6::client | glibc | before 0:2.12-1.149.el6 | 0:2.12-1.149.el6 |
| Red Hat:enterprise_linux:6::client | glibc-common | before 0:2.12-1.149.el6 | 0:2.12-1.149.el6 |
| Red Hat:enterprise_linux:6::client | glibc-debuginfo | before 0:2.12-1.149.el6 | 0:2.12-1.149.el6 |
| Red Hat:enterprise_linux:6::client | glibc-debuginfo-common | before 0:2.12-1.149.el6 | 0:2.12-1.149.el6 |
| Red Hat:enterprise_linux:6::client | glibc-devel | before 0:2.12-1.149.el6 | 0:2.12-1.149.el6 |
| Red Hat:enterprise_linux:6::client | glibc-headers | before 0:2.12-1.149.el6 | 0:2.12-1.149.el6 |
| Red Hat:enterprise_linux:6::client | glibc-static | before 0:2.12-1.149.el6 | 0:2.12-1.149.el6 |
| Red Hat:enterprise_linux:6::client | glibc-utils | before 0:2.12-1.149.el6 | 0:2.12-1.149.el6 |
| Red Hat:enterprise_linux:6::client | nscd | before 0:2.12-1.149.el6 | 0:2.12-1.149.el6 |
Same product
gnu: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4911Glibc: buffer overflow in ld.so leading to privilege escalationKEV80Now
- CVE-2015-0235Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows context-depen68This week
- CVE-2015-7547Multiple stack-based buffer overflows in the (1) send_dg and (2) send_vc functions in the libresolv library in the GNU C Library (aka glibc 59Plan
Published before and after this one in the same product
- ← EarlierCVE-2015-1472Apr 8, 2015 · The ADDW macro in stdio-common/vfscanf.c in the GNU C Library (aka glibc or libc6) before 2.21 does not properly consider data-type size dur31Monitor
- ← EarlierCVE-2015-1473Apr 8, 2015 · The ADDW macro in stdio-common/vfscanf.c in the GNU C Library (aka glibc or libc6) before 2.21 does not properly consider data-type size dur26Monitor
- Later →CVE-2015-1781Sep 28, 2015 · Buffer overflow in the gethostbyname_r and other unspecified NSS functions in the GNU C Library (aka glibc or libc6) before 2.22 allows cont29Monitor
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 |
|---|---|---|
| debian:eglibc | 2.11.3-4+deb6u5 · Debian:6.0 | Package registry (OSV) |
| debian:glibc | 2.15-1 · Debian:12 | Package registry (OSV) |
| red hat:glibc | 0:2.12-1.149.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-common | 0:2.12-1.149.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-debuginfo | 0:2.12-1.149.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-debuginfo-common | 0:2.12-1.149.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-devel | 0:2.12-1.149.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-headers | 0:2.12-1.149.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-static | 0:2.12-1.149.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:glibc-utils | 0:2.12-1.149.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:nscd | 0:2.12-1.149.el6 · Red Hat:enterprise_linux:6::client | 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.
No commit or PR link among the references.
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
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- High
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-17 · DEPRECATED: CodeCVSS vector
AV:N/AC:H/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.