{"answers":{"affected":"2 open source packages ship an affected version, including com.splunk.splunkins:splunk-devops. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10390 in the wild and no public exploit code.","fix":"Upgrade com.splunk.splunkins:splunk-devops to 1.8.0 or later.","what":"CVE-2019-10390 is a high-severity code injection vulnerability in Jenkins Splunk Plugin, published on 28 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10390 and fix it if it is affected.\n\nWhat it is: CVE-2019-10390 is a high-severity code injection vulnerability in Jenkins Splunk Plugin, published on 28 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10390 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.splunk.splunkins:splunk-devops (Maven): affected all versions; fixed in 1.8.0\n- com.splunk.splunkins:splunk-devops (Maven): affected all versions; fixed in 1.8.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-10390/ (Markdown: https://insights.sbomify.com/CVE-2019-10390/index.md)","id":"CVE-2019-10390","markdown":"https://insights.sbomify.com/CVE-2019-10390/index.md","name":"CVE-2019-10390","record":{"aliases":["GHSA-cjr8-5rw4-wh65"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Splunk Plugin","requires_auth":"low_privilege","summary":"Attackers with read permissions can execute arbitrary code on the Jenkins master via a Groovy script injection in the Splunk plugin.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"splunk","vendor":"jenkins"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"A sandbox bypass vulnerability in Jenkins Splunk Plugin 1.7.4 and earlier allowed attackers with Overall/Read permission to provide a Groovy script to an HTTP endpoint that can result in arbitrary code execution on the Jenkins master JVM.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Jenkins Splunk Plugin Sandbox Bypass","id":"CVE-2019-10390","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins IBM AppScan Plugin showed plain text password in job configuration form fields","id":"CVE-2019-10391"},"packages":[{"ecosystem":"Maven","fixed":["1.8.0"],"introduced":["0"],"last_affected":[],"package":"com.splunk.splunkins:splunk-devops","purl":null,"source":"GHSA-cjr8-5rw4-wh65"},{"ecosystem":"Maven","fixed":["1.8.0"],"introduced":["0"],"last_affected":[],"package":"com.splunk.splunkins:splunk-devops","purl":"pkg:maven/com.splunk.splunkins/splunk-devops","source":"GHSA-cjr8-5rw4-wh65"}],"prev":{"headline":"Missing permission check in Jenkins Relution Enterprise Appstore Publisher Plugin","id":"CVE-2019-10389"},"products":["Jenkins Splunk Plugin"],"published":"2019-08-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Jenkins project"]},"summary":"Attackers with read permissions can execute arbitrary code on the Jenkins master via a Groovy script injection in the Splunk plugin.","url":"https://insights.sbomify.com/CVE-2019-10390/"}