How severe is CVE-2015-7547?

CVE-2015-7547 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2015-7547?

Affected package information for CVE-2015-7547 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2015-7547?

No fixed release is recorded for CVE-2015-7547 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2015-7547 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2015-7547 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2015-7547 actively exploited in the wild?

Yes. There are 10 known exploit references for CVE-2015-7547, including 2 documented proof-of-concept exploits on Exploit-DB and 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2015-7547?

CVE-2015-7547 has an EPSS (Exploit Prediction Scoring System) score of 91.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2015-7547?

CVE-2015-7547 is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2015-7547 published, and has it been updated?

CVE-2015-7547 was published on February 18, 2016 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

HIGH severity

CVE-2015-7547 — Red Hat

HIGH

CVE-2015-7547 is a high-severity (CVSS 8.1) Buffer Overflow vulnerability. 10 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Published

Feb 18, 2016

Updated

Apr 16, 2026

Affected

30 products

Patched

See advisory

Exploits

10 known

Exploitation data as of Oct 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

91.0%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2015-7547 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 384,534 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

Multiple 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 or libc6) before 2.23 allow remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted DNS response that triggers a call to the getaddrinfo function with the AF_UNSPEC or AF_INET6 address family, related to performing "dual A/AAAA DNS queries" and the libnss_dns.so.2 NSS module.

Affected Products

30 products · 68 configurations

ubuntu linuxcanonical

3 versions

12.0414.0415.10

debian linuxdebian

1 version

8.0

Application

big-ip access policy managerf5

1 version

12.0.0

Application

big-ip advanced firewall managerf5

1 version

12.0.0

Application

big-ip analyticsf5

1 version

12.0.0

Application

big-ip application acceleration managerf5

1 version

12.0.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-39454doslinux✓ Verified

glibc - 'getaddrinfo' Stack Buffer Overflow (PoC)

by Google Security Research · Feb 16, 2016

Exploit-DB Source

EDB-40339remotelinux

glibc - 'getaddrinfo' Remote Stack Buffer Overflow

by SpeeDr00t · Sep 6, 2016

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2015-7547 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical

After updating the glibc package on affected systems, it is strongly recommended to reboot the system or restart all the affected services. For more information please refer to: https://access.redhat.com/articles/2161461

Product	Fixed in	Advisory
Red Hat Enterprise Linux 6	`glibc-0:2.12-1.166.el6_7.7`	RHSA-2016:0175
Red Hat Enterprise Linux 6.2 Advanced Update Support	`glibc-0:2.12-1.47.el6_2.17`	RHSA-2016:0225
Red Hat Enterprise Linux 7	`glibc-0:2.17-106.el7_2.4`	RHSA-2016:0176
RHEV 3.X Hypervisor and Agents for RHEL-6	`rhev-hypervisor6-0:6.7-20160104.2.el6ev`	RHSA-2016:0277

UbuntuHIGH

USN-2900-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-7547 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2015-7547 — Red Hat

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2015-7547 in your dependencies?