Vulnerabilities in pkg:maven/com.splunk.splunkins/splunk-devops

PACKAGE
Advisory Identifier: GHSA-cjr8-5rw4-wh65
Share
Advisory Summary

CVE-2019-10390 is a HIGH (CVSS 8.8) jenkins splunk plugin sandbox bypass vulnerability (General Security Weakness) affecting Splunk devops libraries in the Maven ecosystem. The issue involves jenkins splunk plugin sandbox bypass. Remediation is available by upgrading affected packages to version 1.8.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/com.splunk.splunkins/splunk-devops

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/com.splunk.splunkins/splunk-devops. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-cjr8-5rw4-wh65 CVE-2019-10390 HIGH Jenkins Splunk Plugin Sandbox Bypass

CVE-2019-10390 at a Glance

CVE Identifier CVE-2019-10390
GHSA Identifier GHSA-cjr8-5rw4-wh65
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification General Security Weakness
Affected Product Splunk devops
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2019-10390

To remediate this vulnerability, upgrade all affected Splunk devops dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

com.splunk.splunkins:splunk-devops fixed: 1.8.0 
<dependency>
    <groupId>com.splunk.splunkins</groupId>
    <artifactId>splunk-devops</artifactId>
    <version>1.8.0</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree -Dincludes=com.splunk.splunkins

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2019-10390, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=com.splunk.splunkins

Analyze the terminal output to locate any version of Splunk devops in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.8.0), your application is affected.

Note: The mvn dependency:tree -Dincludes=com.splunk.splunkins command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Splunk devops, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Jenkins Splunk Plugin has a form validation HTTP endpoint used to validate a user-submitted Groovy script through compilation, which was not subject to sandbox protection. This allowed attackers with Overall/Read access to execute arbitrary code on the Jenkins controller by applying AST transforming annotations such as `@Grab` to source code elements. The affected HTTP endpoint now applies a safe Groovy compiler configuration preventing the use of unsafe AST transforming annotations.

CVE-2019-10390 Affected Splunk devops Versions

1 component(s)
Fixed Versions:
1.8.0
Product / Package Ecosystem Affected Versions Fixed Version
com.splunk.splunkins:splunk-devops
maven/com.splunk.splunkins/splunk-devops
Maven
< 1.8.0
1.8.0

References

NVD — CVE-2019-10390 NVD
https://nvd.nist.gov/vuln/detail/CVE-2019-10390
Security Fix Commit FIX COMMIT
https://github.com/jenkinsci/splunk-devops-plugin/commit/58db2878a7faa4c34f73774f28740e5ac8041928
Splunk devops Security Information SECURITY
https://jenkins.io/security/advisory/2019-08-28/#SECURITY-1294
Splunk devops Security Information SECURITY
http://www.openwall.com/lists/oss-security/2019/08/28/4

Frequently Asked Questions

What is CVE-2019-10390?
CVE-2019-10390 is a security vulnerability in Splunk devops involving Jenkins Splunk Plugin Sandbox Bypass under General Security Weakness.
Which Splunk devops versions are affected?
Affected versions include releases prior to 1.8.0 across affected packages: com.splunk.splunkins:splunk-devops.
What version fixes CVE-2019-10390?
Upgrading to 1.8.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is splunk-devops affected?
Yes, com.splunk.splunkins:splunk-devops is affected in releases prior to 1.8.0. Upgrade your dependency to 1.8.0 or later.
What is the CVSS score of CVE-2019-10390?
CVE-2019-10390 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2019-10390?
CVE-2019-10390 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2019-10390?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=com.splunk.splunkins'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cjr8-5rw4-wh65",
  "modified" : "2023-10-26T23:01:32Z",
  "published" : "2022-05-24T16:55:01Z",
  "aliases" : [ "CVE-2019-10390" ],
  "summary" : "Jenkins Splunk Plugin Sandbox Bypass",
  "details" : "Jenkins Splunk Plugin has a form validation HTTP endpoint used to validate a user-submitted Groovy script through compilation, which was not subject to sandbox protection. This allowed attackers with Overall/Read access to execute arbitrary code on the Jenkins controller by applying AST transforming annotations such as `@Grab` to source code elements.\n\nThe affected HTTP endpoint now applies a safe Groovy compiler configuration preventing the use of unsafe AST transforming annotations.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "com.splunk.splunkins:splunk-devops"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.8.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2019-10390"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jenkinsci/splunk-devops-plugin/commit/58db2878a7faa4c34f73774f28740e5ac8041928"
  }, {
    "type" : "WEB",
    "url" : "https://jenkins.io/security/advisory/2019-08-28/#SECURITY-1294"
  }, {
    "type" : "WEB",
    "url" : "http://www.openwall.com/lists/oss-security/2019/08/28/4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-10-26T23:01:32Z",
    "nvd_published_at" : "2019-08-28T16:15:00Z"
  }
}