What is the CVSS score of CVE-2013-2030?

CVE-2013-2030 has a CVSS 2.0 base score of 2.1 (Low). CVSS vector: AV:L/AC:L/Au:N/C:N/I:P/A:N. EPSS exploitation probability: 0.0%.

Is there a patch available for CVE-2013-2030?

Yes, a patch is available for CVE-2013-2030. Update the affected software to the latest version immediately.

Compute CVE-2013-2030

LOW

Permissions, Privileges, and Access Controls (CWE-264)

2013-12-27 secalert@redhat.com

Privilege Escalation Compute Folsom Grizzly Havana

2.1

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

2.1 LOW

AV:L/AC:L/Au:N/C:N/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:L/AC:L/Au:N/C:N/I:P/A:N

Attack Vector

Local

Attack Complexity

Low

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Dec 27, 2013 - 01:55 cve.org

LOW 2.1

DescriptionCVE.org

keystone/middleware/auth_token.py in OpenStack Nova Folsom, Grizzly, and Havana uses an insecure temporary directory for storing signing certificates, which allows local users to spoof servers by pre-creating this directory, which is reused by Nova, as demonstrated using /tmp/keystone-signing-nova on Fedora.

AnalysisAI

keystone/middleware/auth_token.py in OpenStack Nova Folsom, Grizzly, and Havana uses an insecure temporary directory for storing signing certificates, which allows local users to spoof servers by. Rated low severity (CVSS 2.1), this vulnerability is low attack complexity.

Technical ContextAI

This vulnerability is classified under CWE-264. keystone/middleware/auth_token.py in OpenStack Nova Folsom, Grizzly, and Havana uses an insecure temporary directory for storing signing certificates, which allows local users to spoof servers by pre-creating this directory, which is reused by Nova, as demonstrated using /tmp/keystone-signing-nova on Fedora. Affected products include: Openstack Compute, Openstack Folsom, Openstack Grizzly, Openstack Havana.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.