RHEL 6 : openstack-swift (RHSA-2012:1379)

critical Nessus Plugin ID 210171

Synopsis

The remote Red Hat host is missing a security update for openstack-swift.

Description

The remote Redhat Enterprise Linux 6 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2012:1379 advisory.

OpenStack Swift (http://swift.openstack.org) is a highly available, distributed, eventually consistent object/blob store.

It was found that OpenStack Swift used the Python pickle module in an insecure way to serialize and deserialize data from memcached. As memcached does not have authentication, an attacker on the local network, or possibly an unprivileged user in a virtual machine hosted on OpenStack, could use this flaw to inject specially-crafted data that would lead to arbitrary code execution. (CVE-2012-4406)

Red Hat would like to thank Sebastian Krahmer of the SUSE Security Team for reporting this issue.

Note: The fix for CVE-2012-4406 is not enabled by default, and requires manual action on the affected Proxy nodes. This update adds a memcache_serialization_support option. It is configured in /etc/swift/proxy-server.conf and is set to 0 by default. This default setting is vulnerable to CVE-2012-4406.

To enable the fix, this option must be changed; however, the required changes can have a temporary, large performance impact. The following instructions aim to minimize performance issues:

1) Install the updated openstack-swift packages.

2) In /etc/swift/proxy-server.conf, set the memcache_serialization_support option in the memcache/[filter:cache] section to 1. (The default value, 0, leaves you vulnerable to CVE-2012-4406.) When set to 1, the JSON (JavaScript Object Notation) format is used but pickle is still supported. This configuration is still vulnerable, but new data will be stored in JSON format.

3) After setting the option to 1, run service openstack-swift-proxy restart.

4) After 24 hours, set the memcache_serialization_support option in /etc/swift/proxy-server.conf to 2. 2 is the secure option: only JSON is used.

5) After setting the option to 2, run service openstack-swift-proxy restart.

If memcache_serialization_support is set directly from 0 to 2, all data in memcached will be flushed and re-created. This can lead to a temporary, large performance impact.

All users of openstack-swift are advised to upgrade to these updated packages, which correct this issue.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

Solution

Update the RHEL openstack-swift package based on the guidance in RHSA-2012:1379.

Plugin Details

Severity: Critical

ID: 210171

File Name: redhat-RHSA-2012-1379.nasl

Version: 1.1

Type: local

Agent: unix

Family: Red Hat Local Security Checks

Published: 11/4/2024

Updated: 11/4/2024

Supported Sensors: Agentless Assessment, Continuous Assessment, Frictionless Assessment Agent, Frictionless Assessment AWS, Frictionless Assessment Azure, Nessus Agent, Nessus

Risk Information

VPR

Risk Factor: Medium

Score: 6.7

Vendor

Vendor Severity: Important

CVSS v2

Risk Factor: High

Base Score: 7.5

Temporal Score: 5.5

Vector: CVSS2#AV:N/AC:L/Au:N/C:P/I:P/A:P

CVSS Score Source: CVE-2012-4406

CVSS v3

Risk Factor: Critical

Base Score: 9.8

Temporal Score: 8.5

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C

Vulnerability Information

CPE: p-cpe:/a:redhat:enterprise_linux:openstack-swift-object, p-cpe:/a:redhat:enterprise_linux:openstack-swift-account, p-cpe:/a:redhat:enterprise_linux:openstack-swift, cpe:/o:redhat:enterprise_linux:6, p-cpe:/a:redhat:enterprise_linux:openstack-swift-doc, p-cpe:/a:redhat:enterprise_linux:openstack-swift-proxy, p-cpe:/a:redhat:enterprise_linux:openstack-swift-container

Required KB Items: Host/local_checks_enabled, Host/RedHat/release, Host/RedHat/rpm-list, Host/cpu

Exploit Ease: No known exploits are available

Patch Publication Date: 10/16/2012

Vulnerability Publication Date: 5/30/2012

Reference Information

CVE: CVE-2012-4406

CWE: 502

RHSA: 2012:1379

Detections

Analytics