Security Bulletin: glibc vulnerabilities CVE-2015-5229 and CVE-2015-7547
Security Bulletins ID:
SB10150
Last Modified: 5/4/2022
Last Modified: 5/4/2022
Summary
First Published: February 18, 2016
| Impact of Vulnerability: | Stack-based Buffer Overflow (CWE-121) Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) |
|||
| CVE Information | ||||
| CVE Numbers: | Severity Rating | CVSS v3 Base Score | CVSS v2 Base Score | Affected Products |
| CVE-2015-7547 | High | 8.1 | 6.8 |
|
| CVE-2015-7547 | Critical | 10.0 / 9.5 | 7.9 / 7.9 |
|
| CVE-2015-7547 | Medium | 6.5 | 6.1 |
|
| CVE-2015-5229 | Low | 4.1 / 3.7 | 3.7 / 3.2 |
|
| CVE-2015-5229 | Low | 3.7 | 2.6 |
|
| Highest Base CVSS v3 Score: | 10.0 | |||
| Highest Base CVSS v2 Score: | 7.9 | |||
| Recommendations: | Deploy applicable remediation signatures/rules first. Deploy product updates as they are made available. Implement the Google recommended mitigations |
|||
| Security Bulletin Replacement: | None | |||
| Affected Software: | See the Product Vulnerability Status lists below | |||
| Location of Updated Software: | Product Downloads site | |||
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
Article contents:
Description
CVE-2015-7547: glibc getaddrinfo stack-based buffer overflow
"The glibc DNS client side resolver is vulnerable to a stack-based buffer overflow when the getaddrinfo() library function is used. Software using this function may be exploited with attacker-controlled domain names, attacker-controlled DNS servers, or through a man-in-the-middle attack."
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-7547
CVE-2015-5229: glibc: calloc may return non-zero memory
CERT/CC Vulnerability Note VU# 457759
glibc vulnerable to stack buffer overflow in DNS resolver
http://www.kb.cert.org/vuls/id/457759
CWE-119
Buffer Errors
http://cwe.mitre.org/data/definitions/119.html
CWE-121
Weakness Variant
http://cwe.mitre.org/data/definitions/121.html
According to a Google security blog post:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-7547
Memory areas are returning non-zero bytes. This could result in erratic behavior of applications.
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5229
glibc vulnerable to stack buffer overflow in DNS resolver
http://www.kb.cert.org/vuls/id/457759
CWE-119
Buffer Errors
http://cwe.mitre.org/data/definitions/119.html
Weakness Variant
http://cwe.mitre.org/data/definitions/121.html
Investigation into all products is ongoing. This Security Bulletin will be updated as additional information is available. Not every version of the "Vulnerable and Updated" products are vulnerable. See the Product Specific Notes section below for details. Products not on these lists or on the "No Vulnerabilities Reported" list are being investigated.
Vulnerable and Updated
- Advanced Threat Defense (ATD)
- McAfee Active Response (MAR)
- McAfee Asset Manager (MAM)
- McAfee MOVE AntiVirus Security Virtual Appliance (MOVE SVA)
- McAfee MOVE AntiVirus Security Virtual Appliance Manager (MOVE SVA Manager)
- SaaS Email Archiving (SaaS Archiving)
- SaaS Email Protection and Continuity (SaaS Email)
- Threat Intelligence Exchange (TIE)
- True Key
- VirusScan Enterprise Linux (VSEL)
- Data Exchange Layer (DXL) Framework
- McAfee Email Gateway (MEG)
- Network Data Loss Prevention (NDLP)
- Public Cloud Security (PCS)
Database Activity Monitoring (DAM) GTI Cloud Server GTI Rest Server McAfee MOVE Firewall (MOVE Firewall) McAfee Web Gateway (MWG)
Not Vulnerable
- Capture Service (CS)
- Content Security Reporter (CSR)
- Database Vulnerability Manager (DVM)
- Data Loss Prevention Endpoint (DLPe) / Host Data Loss Prevention (HDLP)
- Endpoint Encryption for PCs (EEPC) / McAfee Drive Encryption (MDE) / Drive Encryption (DE) / Endpoint Encryption Manager (EEM/SafeBoot)
- Endpoint Protection for Mac (EPM)
- Endpoint Security for Mac/ENSM
- Endpoint Solutions Platform (ESP)
- Enterprise Mobility Manager (EMM)
- Email and Web Security (EWS)
- ePO Deep Command (eDC)
- ePolicy Orchestrator (ePO) / ePO Cloud (TPS)
- File and Removable Media Protection (FRP) / Endpoint Encryption for Files and Folders (EEFF) / Endpoint Encryption for Removable Media – USB (EERM)Host Intrusion Prevention System (HIPS) (Windows)
- Management for Optimized Virtual Environments (MOVE) AntiVirus
- McAfee Agent (MA)
- McAfee Application Control (MAC) (See Product Specific Notes)
- McAfee Endpoint Security 10 (ENS)
- McAfee Firewall for Linux
- McAfee Policy Auditor (PA)
- McAfee Quarantine Manager (MQM)
- McAfee Security for Email Servers (MSES)
- McAfee Security for Lotus Domino (MSLD) / Domino Windows (MSDW)
- McAfee Security for Microsoft Exchange (MSME)
- McAfee Security for Microsoft SharePoint (MSMS)
- McAfee Security for Mac (MSM)
- McAfee Security Information and Event Management (SIEM)
- Network Security Manager (NSM)
- Network Security Platform (NSP) Sensor [I, M, and NS-Series]
- Network Threat Behavior Analysis (NTBA)
- McAfee Web Reporter (MWR)
- Vulnerability Manager (MVM)
- Rogue System Detection (RSD)
- SaaS Endpoint Protection (SEP)
- SiteAdvisor Enterprise (SAE) MAC
- SiteAdvisor Enterprise (SAE) Windows
- Total Protection Service Client (ToPS)
- VirusScan Enterprise for Storage (VSES)
- WebAdvisor Consumer
- Whole Disk Encryption (WDE)
- Windows System Security Suite (MTP/MIS/AVP)
No Vulnerabilities Reported
- SaaS Account Management (SAM)
- SaaS Web Protection (SaaS Web)
Remediation
Go to the Product Downloads site and download the applicable product patch/hotfix files:
| Product | Type | Version | File Name | Release Date |
| Advanced Threat Defense (ATD) | Hotfix | 3.4.8.193 | February 29, 2016 | |
| DXL 2.2 | Patch | 2.2 | March 17, 2016 | |
| DXL 2.0.1 | Hotfix | Hotfix 2 (2.0.1.164) | DXLPlatform_2.0.1_Build_164_Package_1_(ENU_LICENSED_RELEASE_BRANCH).zip | February 25, 2016 |
| MAM 6.6 | Hotfix | Hotfix 7 | mam_hotfix_pack7.sh | June 23, 2015 |
| McAfee Active Response (MAR) | Hotfix Iso |
1.1.0.169 | MARPlatform-1.1.0-169.zip MAR-1.1.0.0-169.x86_64.iso |
March 16, 2016 |
| McAfee MOVE AntiVirus Security Virtual Appliance (MOVE SVA) | Cloud Update | N/A | N/A | |
| McAfee MOVE AntiVirus Security Virtual Appliance Manager (MOVE SVA Manager) | Cloud Update | N/A | N/A | |
| SaaS Email Archiving (SaaS Archiving) | Cloud Update | N/A | N/A | February 25, 2016 |
| SaaS Email Protection and Continuity (SaaS Email) | Cloud Update | N/A | N/A | February 25, 2016 |
| TIE 1.2.1 | Hotfix | Hotfix 1 | N/A | February 23, 2016 |
| True Key | Cloud Update | N/A | N/A | February 17, 2016 |
| VirusScan Enterprise Linux (VSEL) | Minor release | 2.0.3 | McAfeeVSEForLinux-2.0.3.29216.zip | June 29,2016 |
Download and Installation Instructions
For instructions to download product updates and hotfixes, see KB56057 - How to download Enterprise product updates and documentation. Review the Release Notes and the Installation Guide for instructions on how to install these updates. All documentation is available on the Product Documentation site.
Product Specific Notes
DXL
Product Exposures:
The only vulnerable DXL component is the DXL Broker Platform. A hotfix will be released to address the vulnerability on the DXL Broker Platform.
This hotfix updates glibc on the DXL Broker Platform to a glibc hotfix removing the vulnerability.
Broker Platforms earlier than DXL 2.0.1 should be updated to DXL 2.0.1 to apply this hotfix.
| DXL Broker Version | CVE-2015-7547 |
| 1.1.0 | Vulnerable |
| 2.0 | Vulnerable |
| 2.0.1 | Hotfixes |
MAC
McAfee Application Control does not use the getaddrinfo() function in the manner that is the trigger of the vulnerable code execution. The vulnerable code applies when DNS is involved, but MAC does not query/listen for anything outside the native components
Mitigations
The vulnerability can be mitigated by the following steps as provided by Google:
"Google has found some mitigations that may help prevent exploitation if you are not able to immediately patch your instance of glibc. The vulnerability relies on an oversized (2048+ bytes) UDP or TCP response, which is followed by another response that will overwrite the stack. Our suggested mitigation is to limit the response (using DNSMasq or similar programs) sizes accepted by the DNS resolver locally as well as to ensure that DNS queries are sent only to DNS servers that limit the response size for UDP responses with the truncation bit set."
Acknowledgements
These vulnerabilities were first disclosed by Google and RedHat:
https://rhn.redhat.com/errata/RHSA-2016-0176.html
https://googleonlinesecurity.blogspot.com/2016/02/cve-2015-7547-glibc-getaddrinfo-stack.html
https://rhn.redhat.com/errata/RHSA-2016-0176.html
https://googleonlinesecurity.blogspot.com/2016/02/cve-2015-7547-glibc-getaddrinfo-stack.html
Frequently Asked Questions (FAQs)
How do I know whether my product is vulnerable?
For Endpoint products:
Use the following instructions for endpoint or client based products:
Check the version and build of ePO that is installed. For information on how to check the version, see KB52634.
For Appliances:
Use the following instructions for Appliance based products:What is CVSS?
CVSS, or Common Vulnerability Scoring System, is the result of the National Infrastructure Advisory Council’s effort to standardize a system of assessing the criticality of a vulnerability. This system offers an unbiased criticality score between 0 and 10 that customers can use to judge how critical a vulnerability is and plan accordingly. For more information, please visit the CVSS website.
When calculating CVSS v2 scores, we've adopted a philosophy that fosters consistency and repeatability. Our guiding principle for CVSS scoring is to score the exploit under consideration by itself. We consider only the immediate and direct impact of the exploit under consideration. We do not factor into a score any potential follow-on exploits that might be made possible by successful exploitation of the issue being scored.
CVSS v3 scoring is in final review as of December 2015. CVSS v2 will be replaced with CVSS v3 when v3 is fully approved. Security bulletins will have scores for both versions for at least 6 months after v3 is fully approved.
https://www.first.org/cvss/v3/development
https://www.first.org/cvss/calculator/3.0
What are the CVSS scoring metrics that have been used?
CVE-2015-7547: glibc getaddrinfo stack-based buffer overflow
CVSS v3 Scoring:
NOTE: The below CVSS version 3.0 vector was used to generate this score.
https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L
CVSS v2.0 Scoring:
For Endpoint products:
Use the following instructions for endpoint or client based products:
- Right-click on the McAfee tray shield icon on the Windows task bar.
- Select Open Console.
- In the console, select Action Menu.
- In the Action Menu, select Product Details. The product version is displayed.
Check the version and build of ePO that is installed. For information on how to check the version, see KB52634.
For Appliances:
Use the following instructions for Appliance based products:
- Open the Administrator's User Interface (UI).
- Click the About link. The product version is displayed.
CVSS, or Common Vulnerability Scoring System, is the result of the National Infrastructure Advisory Council’s effort to standardize a system of assessing the criticality of a vulnerability. This system offers an unbiased criticality score between 0 and 10 that customers can use to judge how critical a vulnerability is and plan accordingly. For more information, please visit the CVSS website.
When calculating CVSS v2 scores, we've adopted a philosophy that fosters consistency and repeatability. Our guiding principle for CVSS scoring is to score the exploit under consideration by itself. We consider only the immediate and direct impact of the exploit under consideration. We do not factor into a score any potential follow-on exploits that might be made possible by successful exploitation of the issue being scored.
CVSS v3 scoring is in final review as of December 2015. CVSS v2 will be replaced with CVSS v3 when v3 is fully approved. Security bulletins will have scores for both versions for at least 6 months after v3 is fully approved.
https://www.first.org/cvss/v3/development
https://www.first.org/cvss/calculator/3.0
| Base Score | 6.5 |
| Attack Vector (AV) | Network (N) |
| Attack Complexity (AC) | High (H) |
| Privileges Required (PR) | None (N) |
| User Interaction (UI) | None (N) |
| Scope (S) | Unchanged (U) |
| Confidentiality (C) | None (N) |
| Integrity (I) | High (H) |
| Availability (A) | Low (L) |
NOTE: The below CVSS version 3.0 vector was used to generate this score.
https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L
CVSS v2.0 Scoring:
| Base Score | 6.1 |
| Related exploit range (AccessVector) | Network (N) |
| Attack complexity (AccessComplexity) | High (H) |
| Level of authentication needed (Authentication) | None (N) |
| Confidentiality impact | None (N) |
| Integrity impact | Complete (C) |
| Availability impact | Partial (P) |
NOTE: The below CVSS version 2.0 vector was used to generate this score.
https://nvd.nist.gov/cvss.cfm?calculator&version=2&vector=%20(AV:N/AC:H/Au:N/C:N/I:C/A:P)%20%20
| Base Score | 3.7 |
| Attack Vector (AV) | Network (N) |
| Attack Complexity (AC) | High (H) |
| Privileges Required (PR) | None (N) |
| User Interaction (UI) | None (N) |
| Scope (S) | Unchanged (U) |
| Confidentiality (C) | None (N) |
| Integrity (I) | High (H) |
| Availability (A) | Low (L) |
NOTE: The below CVSS version 3.0 vector was used to generate this score.
https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
CVSS v2.0 Scoring:
| Base Score | 2.6 |
| Related exploit range (AccessVector) | Network (N) |
| Attack complexity (AccessComplexity) | High (H) |
| Level of authentication needed (Authentication) | None (N) |
| Confidentiality impact | None (N) |
| Integrity impact | None (N) |
| Availability impact | Partial (P) |
NOTE: The below CVSS version 2.0 vector was used to generate this score.
https://nvd.nist.gov/cvss.cfm?calculator&version=2&vector=(AV:N/AC:H/Au:N/C:N/I:N/A:P)
Where can I find a list of all Security Bulletins?
All Security Bulletins are published on our Knowledge Center. Security Bulletins are retired (removed) once a product is both End of Sale and End of Support (End of Life).
How do I report a product vulnerability to you?
If you have information about a security issue or vulnerability with a product, follow the instructions provided in KB95563 - Report a vulnerability.
How do you respond to this and any other reported security flaws?
Our key priority is the security of our customers. If a vulnerability is found within any of our software or services, we work closely with the relevant security software development team to ensure the rapid and effective development of a fix and communication plan.
We only publish Security Bulletins if they include something actionable such as a workaround, mitigation, version update, or hotfix. Otherwise, we would simply be informing the hacker community that our products are a target, putting our customers at greater risk. For products that are updated automatically, a non-actionable Security Bulletin might be published to acknowledge the discoverer.
To view our PSIRT policy, see KB95564 - About PSIRT.
Resources
To contact Technical Support, go to the Create a Service Request page and log on to the ServicePortal.
- If you are a registered user, type your User ID and Password, and then click Log In.
- If you are not a registered user, click Register and complete the fields to have your password and instructions emailed to you.
Disclaimer
The information provided in this Security Bulletin is provided as is without warranty of any kind. We disclaim all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall we or our suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits, or special damages, even if we or our suppliers have been advised of the possibility of such damages. Some states don't allow the exclusion or limitation of liability for consequential or incidental damages, so the preceding limitation may not apply.
Any future product release dates mentioned in this Security Bulletin are intended to outline our general product direction, and they shouldn't be relied on in making a purchasing decision. The product release dates are for information purposes only, and may not be incorporated into any contract. The product release dates aren't a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remain at our sole discretion and may be changed or canceled at any time.
Any future product release dates mentioned in this Security Bulletin are intended to outline our general product direction, and they shouldn't be relied on in making a purchasing decision. The product release dates are for information purposes only, and may not be incorporated into any contract. The product release dates aren't a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remain at our sole discretion and may be changed or canceled at any time.
