CVE-2015-1820 Vulnerability Analysis & Exploit Details

CVE-2015-1820
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2015-1820 has severe implications, demanding immediate intervention.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2015-1820 Details

Status: Modified

Last updated: 🕑 21 Nov 2024, 02:26 UTC
Originally published on: 🕕 09 Aug 2017, 18:29 UTC

Time between publication and last update: 2660 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2015-1820 Vulnerability Summary

CVE-2015-1820: REST client for Ruby (aka rest-client) before 1.8.0 allows remote attackers to conduct session fixation attacks or obtain sensitive cookie information by leveraging passage of cookies set in a response to a redirect.

Assessing the Risk of CVE-2015-1820

Access Complexity Graph

The exploitability of CVE-2015-1820 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-2015-1820

With low attack complexity and no required privileges, CVE-2015-1820 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

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-2015-1820, 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-2015-1820, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2015-1820 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2015-1820 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2015-1820 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

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

EPSS Score: 0.671% (probability of exploit)

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

CVE-2015-1820 References

External References

CWE Common Weakness Enumeration

CWE-384

CAPEC Common Attack Pattern Enumeration and Classification

  • Session Credential Falsification through Forging CAPEC-196 An attacker creates a false but functional session credential in order to gain or usurp access to a service. Session credentials allow users to identify themselves to a service after an initial authentication without needing to resend the authentication information (usually a username and password) with every message. If an attacker is able to forge valid session credentials they may be able to bypass authentication or piggy-back off some other authenticated user's session. This attack differs from Reuse of Session IDs and Session Sidejacking attacks in that in the latter attacks an attacker uses a previous or existing credential without modification while, in a forging attack, the attacker must create their own credential, although it may be based on previously observed credentials.
  • Exploitation of Trusted Identifiers CAPEC-21 An adversary guesses, obtains, or "rides" a trusted identifier (e.g. session ID, resource ID, cookie, etc.) to perform authorized actions under the guise of an authenticated user or service.
  • Accessing/Intercepting/Modifying HTTP Cookies CAPEC-31 This attack relies on the use of HTTP Cookies to store credentials, state information and other critical data on client systems. There are several different forms of this attack. The first form of this attack involves accessing HTTP Cookies to mine for potentially sensitive data contained therein. The second form involves intercepting this data as it is transmitted from client to server. This intercepted information is then used by the adversary to impersonate the remote user/session. The third form is when the cookie's content is modified by the adversary before it is sent back to the server. Here the adversary seeks to convince the target server to operate on this falsified information.
  • Manipulating Opaque Client-based Data Tokens CAPEC-39 In circumstances where an application holds important data client-side in tokens (cookies, URLs, data files, and so forth) that data can be manipulated. If client or server-side application components reinterpret that data as authentication tokens or data (such as store item pricing or wallet information) then even opaquely manipulating that data may bear fruit for an Attacker. In this pattern an attacker undermines the assumption that client side tokens have been adequately protected from tampering through use of encryption or obfuscation.
  • Session Credential Falsification through Prediction CAPEC-59 This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Reusing Session IDs (aka Session Replay) CAPEC-60 This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
  • Session Fixation CAPEC-61 The attacker induces a client to establish a session with the target software using a session identifier provided by the attacker. Once the user successfully authenticates to the target software, the attacker uses the (now privileged) session identifier in their own transactions. This attack leverages the fact that the target software either relies on client-generated session identifiers or maintains the same session identifiers after privilege elevation.

Vulnerable Configurations

  • cpe:2.3:a:rest-client_project:rest-client:0.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.3:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.3:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.4:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.4:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.5:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.5:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.5.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.5.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.6:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.6:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.6.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.6.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.6.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.6.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.7:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.7:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.8:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.8:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.8.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.8.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.8.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.8.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.9:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.9:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:0.9.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:0.9.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.0.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.0.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.0.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.0.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.0.3:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.0.3:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.0.4:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.0.4:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.1.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.1.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.2.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.2.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.3.0:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.3.0:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.3.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.3.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.4.0:-:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.4.0:-:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.4.0:alpha:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.4.0:alpha:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.4.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.4.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.4.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.4.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.5.0:-:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.5.0:-:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.5.0:beta:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.5.0:beta:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.5.0:alpha:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.5.0:alpha:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.5.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.5.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.0:-:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.0:-:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.0:alpha:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.0:alpha:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.1:-:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.1:-:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.1:alpha:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.1:alpha:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.2:-:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.2:-:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.2:alpha:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.2:alpha:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.3:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.3:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.5:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.5:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.6:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.6:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.7:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.7:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.8:-:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.8:-:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.8:rc1:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.8:rc1:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.9:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.9:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.10:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.10:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.11:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.11:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.12:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.12:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.13:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.13:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.6.14:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.6.14:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.7.0:-:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.7.0:-:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.7.0:rc1:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.7.0:rc1:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.7.1:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.7.1:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.7.2:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.7.2:*:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.7.2:-:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.7.2:-:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.7.2:rc1:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.7.2:rc1:*:*:*:ruby:*:*
  • cpe:2.3:a:rest-client_project:rest-client:1.7.3:*:*:*:*:ruby:*:*
    cpe:2.3:a:rest-client_project:rest-client:1.7.3:*:*:*:*:ruby:*:*

Protect Your Infrastructure against CVE-2015-1820: 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-2024-43107 – Improper Certificate Validation (CWE-295) in the Gallagher Milestone Integration Plugin (MIP) permits unauthenticated messages (e.g. alarm events) ...
  • CVE-2024-41724 – Improper Certificate Validation (CWE-295) in the Gallagher Command Centre SALTO integration allowed an attacker to spoof the SALTO server. Thi...
  • CVE-2025-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
  • CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
  • CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...