Menu

Star on GitHub · 3.2k

CVE-2013-1815

6.1 · MEDIUM

A flaw was found in PackStack.

Published Apr 10, 2013redhatCWE-379EPSS 0.45%

Overview

CVE-2013-1815 is a medium-severity vulnerability affecting redhat openstack_essex. It was published on April 10, 2013 and has a CVSS 3.1 base score of 6.1 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 6.1, rated MEDIUM. 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. This vulnerability allows a local user to modify deployed systems by changing the answer file, which is created in insecure directories such as /tmp or the current working directory. This insecure file creation could lead to unauthorized system modifications.

Remediation

Check the references section for vendor advisories and patches from redhat. Update openstack_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-1815?

CVE-2013-1815 is a medium-severity vulnerability affecting redhat openstack_essex. It was published on April 10, 2013 and has a CVSS 3.1 base score of 6.1 (MEDIUM).

How severe is CVE-2013-1815?

This vulnerability has a CVSS 3.1 base score of 6.1, rated MEDIUM. 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-1815?

Check the references section for vendor advisories and patches from redhat. Update openstack_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-1815?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2013-1815 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 MEDIUM CVEs from 2013

View all