CVE-2017-1000096 Vulnerability Analysis & Exploit Details

CVE-2017-1000096
Vulnerability Scoring

8.8
/10
Severe Risk

Cybersecurity professionals consider CVE-2017-1000096 an immediate threat requiring urgent mitigation.

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: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2017-1000096 Details

Status: Modified

Last updated: 🕒 21 Nov 2024, 03:04 UTC
Originally published on: 🕐 05 Oct 2017, 01:29 UTC

Time between publication and last update: 2604 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2017-1000096 Vulnerability Summary

CVE-2017-1000096: Arbitrary code execution due to incomplete sandbox protection: Constructors, instance variable initializers, and instance initializers in Pipeline scripts were not subject to sandbox protection, and could therefore execute arbitrary code. This could be exploited e.g. by regular Jenkins users with the permission to configure Pipelines in Jenkins, or by trusted committers to repositories containing Jenkinsfiles.

Assessing the Risk of CVE-2017-1000096

Access Complexity Graph

The exploitability of CVE-2017-1000096 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-2017-1000096

CVE-2017-1000096 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

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-2017-1000096, 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-2017-1000096, 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-2017-1000096 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2017-1000096 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2017-1000096 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.131% (probability of exploit)

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

CVE-2017-1000096 References

External References

CWE Common Weakness Enumeration

CWE-732

CAPEC Common Attack Pattern Enumeration and Classification

  • Accessing Functionality Not Properly Constrained by ACLs CAPEC-1 In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.
  • 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.
  • Directory Indexing CAPEC-127 An adversary crafts a request to a target that results in the target listing/indexing the content of a directory as output. One common method of triggering directory contents as output is to construct a request containing a path that terminates in a directory name rather than a file name since many applications are configured to provide a list of the directory's contents when such a request is received. An adversary can use this to explore the directory tree on a target as well as learn the names of files. This can often end up revealing test files, backup files, temporary files, hidden files, configuration files, user accounts, script contents, as well as naming conventions, all of which can be used by an attacker to mount additional attacks.
  • Using Malicious Files CAPEC-17 An attack of this type exploits a system's configuration that allows an adversary to either directly access an executable file, for example through shell access; or in a possible worst case allows an adversary to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Exploiting Incorrectly Configured Access Control Security Levels CAPEC-180 An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack.
  • Signing Malicious Code CAPEC-206 The adversary extracts credentials used for code signing from a production environment and then uses these credentials to sign malicious content with the developer's key. Many developers use signing keys to sign code or hashes of code. When users or applications verify the signatures are accurate they are led to believe that the code came from the owner of the signing key and that the code has not been modified since the signature was applied. If the adversary has extracted the signing credentials then they can use those credentials to sign their own code bundles. Users or tools that verify the signatures attached to the code will likely assume the code came from the legitimate developer and install or run the code, effectively allowing the adversary to execute arbitrary code on the victim's computer. This differs from CAPEC-673, because the adversary is performing the code signing.
  • Hijacking a privileged process CAPEC-234 An adversary gains control of a process that is assigned elevated privileges in order to execute arbitrary code with those privileges. Some processes are assigned elevated privileges on an operating system, usually through association with a particular user, group, or role. If an attacker can hijack this process, they will be able to assume its level of privilege in order to execute their own code.
  • 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.
  • Cross Site Request Forgery CAPEC-62 An attacker crafts malicious web links and distributes them (via web pages, email, etc.), typically in a targeted manner, hoping to induce users to click on the link and execute the malicious action against some third-party application. If successful, the action embedded in the malicious link will be processed and accepted by the targeted application with the users' privilege level. This type of attack leverages the persistence and implicit trust placed in user session cookies by many web applications today. In such an architecture, once the user authenticates to an application and a session cookie is created on the user's system, all following transactions for that session are authenticated using that cookie including potential actions initiated by an attacker and simply "riding" the existing session cookie.
  • Replace Binaries CAPEC-642 Adversaries know that certain binaries will be regularly executed as part of normal processing. If these binaries are not protected with the appropriate file system permissions, it could be possible to replace them with malware. This malware might be executed at higher system permission levels. A variation of this pattern is to discover self-extracting installation packages that unpack binaries to directories with weak file permissions which it does not clean up appropriately. These binaries can be replaced by malware, which can then be executed.

Vulnerable Configurations

  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.0:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.0:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.1:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.1:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.2:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.2:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.3:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.3:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.4:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.4:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.4.1:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.4.1:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.4.2:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.4.2:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.4.3:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.4.3:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.5:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.5:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.6:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.6:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.7:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.7:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.8:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.8:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.9:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.9:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.10:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.10:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.10.1:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.10.1:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.11:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.11:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.12:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.12:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.13:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.13:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.14:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.14:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.14.1:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.14.1:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.14.2:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.14.2:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:1.15:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:1.15:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.0:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.0:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.1:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.1:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.2:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.2:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.3:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.3:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.4:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.4:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.5:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.5:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.6:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.6:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.7:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.7:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.8:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.8:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.9:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.9:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.10:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.10:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.11:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.11:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.12:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.12:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.13:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.13:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.14:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.14:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.15:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.15:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.16:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.16:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.17:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.17:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.18:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.18:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.19:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.19:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.20:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.20:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.21:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.21:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.22:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.22:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.23:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.23:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.24:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.24:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.25:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.25:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.26:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.26:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.27:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.27:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.28:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.28:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.29:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.29:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.30:-:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.30:-:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.30:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.30:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.30:beta:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.30:beta:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.30:alpha:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.30:alpha:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.30:alpha2:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.30:alpha2:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.31:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.31:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.32:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.32:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.33:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.33:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.34:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.34:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.35:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.35:*:*:*:*:jenkins:*:*
  • cpe:2.3:a:jenkins:pipeline\:_groovy:2.36:*:*:*:*:jenkins:*:*
    cpe:2.3:a:jenkins:pipeline\:_groovy:2.36:*:*:*:*:jenkins:*:*

Protect Your Infrastructure against CVE-2017-1000096: 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-3809 – The Debug Log Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the auto-refresh debug log in all versions up to, and i...
  • CVE-2025-2111 – The Insert Headers And Footers plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.1.1. This i...
  • CVE-2024-13926 – The WP-Syntax WordPress plugin through 1.2 does not properly handle input, allowing an attacker to create a post containing a large number of tags,...
  • CVE-2025-3103 – The CLEVER - HTML5 Radio Player With History - Shoutcast and Icecast - Elementor Widget Addon plugin for WordPress is vulnerable to arbitrary file ...
  • CVE-2025-3275 – The Themesflat Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the TF E Slider widget in all versions up...