CVE-2019-10354: Missing Authorization in Jenkins

CVE-2019-10354 · Severity: low · CVSS 3.1 · Published 2022-05-24

Missing Authorization in Jenkins

Technologies: org.jenkins-ci.main:jenkins-core (Maven), org.kohsuke.stapler:stapler-parent (Maven). Vendors: Maven.

Quick answers

Is CVE-2019-10354 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-10354 being exploited in the wild.
How severe is CVE-2019-10354?
Low severity, with a CVSS score of 3.1, published 24 May 2022.
Which products and versions are affected?
org.jenkins-ci.main:jenkins-core (Maven) ECOSYSTEM:introduced=0,fixed=2.176.2; org.kohsuke.stapler:stapler-parent (Maven) ECOSYSTEM:introduced=0,fixed=1.257.1.
Is there a fix for CVE-2019-10354?
Yes. org.jenkins-ci.main:jenkins-core (Maven): upgrade to 2.176.2 or later; org.kohsuke.stapler:stapler-parent (Maven): upgrade to 1.257.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-10354?
Check whether you run org.jenkins-ci.main:jenkins-core (Maven) or org.kohsuke.stapler:stapler-parent (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.jenkins-ci.main:jenkins-core (Maven): upgrade to 2.176.2 or later
    # set org.jenkins-ci.main:jenkins-core to 2.176.2 in your pom.xml or build.gradle
  • org.kohsuke.stapler:stapler-parent (Maven): upgrade to 1.257.1 or later
    # set org.kohsuke.stapler:stapler-parent to 1.257.1 in your pom.xml or build.gradle

Affected products

  • org.jenkins-ci.main:jenkins-core (Maven) ECOSYSTEM:introduced=0,fixed=2.176.2
  • org.kohsuke.stapler:stapler-parent (Maven) ECOSYSTEM:introduced=0,fixed=1.257.1

Identifiers

  • CVE-2019-10354
  • GHSA-6jfc-mc97-c7wg

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.