CVE-2013-6391 Vulnerability Analysis & Exploit Details

CVE-2013-6391
Vulnerability Scoring

5.8
/10
Significant Risk

Security teams should be aware that CVE-2013-6391 may be exploited under specific circumstances, requiring timely patches.

Attack Complexity Details

  • Attack Complexity: Medium
    Attack Complexity Analysis In Progress
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No authentication is required for exploitation.
  • Scope:
    Impact is confined to the initially vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2013-6391 Details

Status: Modified

Last updated: 🕜 21 Nov 2024, 01:59 UTC
Originally published on: 🕔 14 Dec 2013, 17:21 UTC

Time between publication and last update: 3994 days

CVSS Release: version 2

CVE-2013-6391 Vulnerability Summary

CVE-2013-6391: The ec2tokens API in OpenStack Identity (Keystone) before Havana 2013.2.1 and Icehouse before icehouse-2 does not return a trust-scoped token when one is received, which allows remote trust users to gain privileges by generating EC2 credentials from a trust-scoped token and using them in an ec2tokens API request.

Assessing the Risk of CVE-2013-6391

Access Complexity Graph

The exploitability of CVE-2013-6391 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2013-6391

Moderate complexity but no authentication required makes CVE-2013-6391 a potential risk.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2013-6391, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2013-6391, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2013-6391 does not compromise confidentiality.
  • Integrity: None
    CVE-2013-6391 does not impact data integrity.
  • Availability: None
    CVE-2013-6391 does not affect system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.176% (probability of exploit)

EPSS Percentile: 55.8% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 44.2% of others.

CVE-2013-6391 References

External References

CWE Common Weakness Enumeration

CWE-269

CAPEC Common Attack Pattern Enumeration and Classification

  • Privilege Abuse CAPEC-122 An adversary is able to exploit features of the target that should be reserved for privileged users or administrators but are exposed to use by lower or non-privileged accounts. Access to sensitive information and functionality must be controlled to ensure that only authorized users are able to access these resources.
  • Privilege Escalation CAPEC-233 An adversary exploits a weakness enabling them to elevate their privilege and perform an action that they are not supposed to be authorized to perform.
  • Restful Privilege Elevation CAPEC-58 An adversary identifies a Rest HTTP (Get, Put, Delete) style permission method allowing them to perform various malicious actions upon server data due to lack of access control mechanisms implemented within the application service accepting HTTP messages.

Vulnerable Configurations

  • cpe:2.3:a:openstack:keystone:2013.2:*:*:*:*:*:*:*
    cpe:2.3:a:openstack:keystone:2013.2:*:*:*:*:*:*:*
  • cpe:2.3:o:canonical:ubuntu_linux:13.10:*:*:*:*:*:*:*
    cpe:2.3:o:canonical:ubuntu_linux:13.10:*:*:*:*:*:*:*
  • cpe:2.3:a:redhat:openstack:4.0:*:*:*:*:*:*:*
    cpe:2.3:a:redhat:openstack:4.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2013-6391: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...