Menu

Star on GitHub · 3.2k

CVE-2013-0261

8.8 · HIGH

A flaw was found in PackStack.

Published Mar 8, 2013openstackCWE-59EPSS 0.34%

Overview

CVE-2013-0261 is a high-severity vulnerability affecting openstack essex. It was published on March 8, 2013 and has a CVSS 3.1 base score of 8.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

A flaw was found in PackStack. A local user could exploit a symlink attack on a temporary file with a predictable name in the `/tmp` directory. This vulnerability allows the local user to overwrite arbitrary files on the system, potentially leading to system compromise or data corruption.

Remediation

Check the references section for vendor advisories and patches from openstack. Update essex to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2013-0261?

CVE-2013-0261 is a high-severity vulnerability affecting openstack essex. It was published on March 8, 2013 and has a CVSS 3.1 base score of 8.8 (HIGH).

How severe is CVE-2013-0261?

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2013-0261?

Check the references section for vendor advisories and patches from openstack. Update essex to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2013-0261?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2013-0261 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2013

View all