Security Bulletin: Vulnerability in Open Source GNU glibc affects IBM OS Images for Red Hat Linux Systems. (CVE-2013-7423)

Summary

A vulnerability in Open Source GNU glibc affects IBM OS Images for Red Hat Linux Systems.

Vulnerability Details

CVEID: CVE-2013-7423 DESCRIPTION: GNU glibc could allow a local attacker to obtain sensitive information, caused by the writing of DNS queries to random file descriptors under high load by the getaddrinfo() function. An attacker could exploit this vulnerability to obtain sensitive information.

CVSS Base Score: 1.2
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100647 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:L/AC:H/Au:N/C:P/I:N/A:N)

Affected Products and Versions

IBM OS Image for Red Hat Linux Systems 2.0
IBM OS Image for Red Hat Linux Systems 2.0.0.1
IBM OS Image for Red Hat Linux Systems 2.0.0.2
IBM OS Image for Red Hat Linux Systems 2.0.0.3
IBM OS Image for Red Hat Linux Systems 2.0.0.4
IBM OS Image for Red Hat Linux Systems 2.1.0.0
IBM OS Image for Red Hat Linux Systems 2.1.0.1
IBM OS Image for Red Hat Linux Systems 2.1.0.2

Remediation/Fixes

The deployed Red Hat Linux-based virtual machines on IBM PureApplication System types are affected. The solution is to apply the following emergency fix to the deployed virtual machines.

http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=2.0.0.1&platform=All&function=fixId&fixids=glibc_patch&includeSupersedes=0

1. Import the fix into the Emergency Fix catalogue.
2. For deployed instances, apply this emergency fix on the VM. The glibc library on the IBM OS Image for Red Hat Linux Systems will be updated to contain the fix.
3. Restart the deployed instance after the fix is applied.

Optionally, the operating system vendor provides a glibc fix. The fix can be applied by running the command “yum update glibc” within the deployed virtual machine to upgrade to the latest glibc version.

You should verify applying this fix does not cause any compatibility issues.

Workarounds and Mitigations

None