What is CVE-2015-7547?A high-severity flaw in Glibc, explained.
CVE-2015-7547 is a high-severity flaw (CVSS 8.1) in Glibc from Gnu, published on 18 February 2016. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 91%. If you run an affected version, plan in the vendor’s fix.
Published 18 February 2016. Record last updated 12 April 2025. We keep this page's data up to date.
What is CVE-2015-7547? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
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.
What kind of flaw is it?
- CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offHard: conditions must line up
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Is CVE-2015-7547 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 91%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2015-7547 scores 71. Action: Patch now.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2015-7547 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2015-7547? 30 products.
The published record lists 30 products from 10 vendors. If you run one of these, check your version, then go to the fix below.
- Application
Glibc
by Gnu
Affected versions2.92.102.10.12.112.11.12.11.22.11.32.122.12.12.12.22.132.142.14.12.15 - Operating system
Linux Enterprise Desktop
by Suse
Affected versions11.0-sp311.0-sp41212-sp1 - Operating system
Linux Enterprise Server
by Suse
Affected versions11.0-sp211.0-sp311.0-sp412-sp1 - Operating system
Linux Enterprise Software Development Kit
by Suse
Affected versions11.0-sp311.0-sp41212-sp1 - Application
Helion Openstack
by HP
Affected versions1.1.12.0.02.1.0 - Application
Linux Enterprise Debuginfo
by Suse
Affected versions11.0-sp211.0-sp311.0-sp4 - Operating system
Ubuntu Linux
by Canonical
Affected versions12.0414.0415.10 - Application
Exalogic Infrastructure
by Oracle
Affected versions1.02.0 - Application
Unified Threat Management Software
by Sophos
Affected versions9.3199.355
How do I fix CVE-2015-7547? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
49 links- Cpuapr2016v3 2985753 (opens in a new tab)oracle.com
- Glibc Getaddrinfo Stack Overflow (opens in a new tab)fortiguard.com
- February (opens in a new tab)fedoraproject.org · 2016
- February (opens in a new tab)fedoraproject.org · 2016
- Msg00036 (opens in a new tab)opensuse.org · 2016
- Msg00037 (opens in a new tab)opensuse.org · 2016
Does CVE-2015-7547 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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 ...
- Matched to
- Glibc on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2015-7547 is a high-severity flaw in Glibc from Gnu, published on 18 February 2016. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 8.1 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2015-7547 is 71 out of 100, which is High. Its action is "Patch now". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 91%. That can change at any time, which is why we keep watching.
For Glibc from Gnu: 2.9, 2.10, 2.10.1, 2.11, 2.11.1, 2.11.2 and 15 more. The record lists 30 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.