Eric Windisch

**Name of the Vulnerable Software and Affected Versions** Docker Engine versions prior to 1.6.1 **Description** The issue allows local users to modify the host, obtain sensitive information, and perform protocol downgrade attacks via a crafted image. This is due to weak permissions for certain /proc files, including `/proc/asound`, `/proc/timer stats`, `/proc/latency stats`, and `/proc/fs`. **Recommendations** For Docker Engine versions prior to 1.6.1, update to version 1.6.1 or later to resolve the issue. As a temporary workaround, consider restricting access to the vulnerable /proc files to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Docker Engine versions prior to 1.6.1 **Description** The issue allows local users to set arbitrary Linux Security Modules (LSM) and docker t policies via an image that allows volumes to override files in /proc. This can be achieved by exploiting the ability of Docker Engine to allow volumes to override files in the /proc directory, potentially leading to unauthorized access or modifications to system configurations. **Recommendations** For Docker Engine versions prior to 1.6.1, update to version 1.6.1 or later to resolve the issue. As a temporary workaround, consider restricting the use of volumes that can override files in /proc to minimize the risk of exploitation. Avoid using images that allow volumes to override sensitive system files until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Red Hat docker package versions prior to 1.5.0-28 **Description** The issue allows man-in-the-middle attackers to conduct downgrade attacks and obtain authentication and image data by leveraging a network position between the client and the registry to block HTTPS traffic. This occurs when the Red Hat docker package falls back to HTTP after an HTTPS connection to the registry fails, specifically when using the --add-registry option. **Recommendations** For versions prior to 1.5.0-28, update to version 1.5.0-28 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** OpenStack Compute (Nova) versions prior to 2012.2.2 OpenStack Compute (Nova) version Grizzly **Description** The issue allows attackers to obtain sensitive information by reading the memory of the previous logical volume (LV) when using libvirt and LVM backed instances. This occurs because the physical volume (PV) content is not properly cleared when reallocating for instances. **Recommendations** For OpenStack Compute (Nova) versions prior to 2012.2.2, update to version 2012.2.2 or later to resolve the issue. For OpenStack Compute (Nova) version Grizzly, at the moment, there is no information about a newer version that contains a fix for this vulnerability.