Is CVE-2018-1000861 exploited in the wild?

Yes. CVE-2018-1000861 is known to be exploited in the wild, first recorded on 10 February 2022. Treat it as urgent.

How severe is CVE-2018-1000861?

Critical severity, with a CVSS score of 3, published 13 May 2022.

Which products and versions are affected?

org.jenkins-ci.main:jenkins-core (Maven) ECOSYSTEM:introduced=0,fixed=2.138.4.

Is there a fix for CVE-2018-1000861?

Yes. org.jenkins-ci.main:jenkins-core (Maven): upgrade to 2.138.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2018-1000861 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2018-1000861?

Check whether you run Jenkins Stapler Web Framework or org.jenkins-ci.main:jenkins-core (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.

CVE-2018-1000861: Deserialization of Untrusted Data in Jenkins

CVE-2018-1000861 · Severity: critical · CVSS 3 · Exploited in the wild · Published 2022-05-13

A deserialization of untrusted data vulnerability in the Stapler web framework used by Jenkins allows remote attackers to invoke unintended methods on Java objects via crafted URLs. This can lead to arbitrary code execution on the affected Jenkins server.

Technologies: org.jenkins-ci.main:jenkins-core (Maven). Vendors: Jenkins, Maven.

Quick answers

Is CVE-2018-1000861 exploited in the wild?: Yes. CVE-2018-1000861 is known to be exploited in the wild, first recorded on 10 February 2022. Treat it as urgent.
How severe is CVE-2018-1000861?: Critical severity, with a CVSS score of 3, published 13 May 2022.
Which products and versions are affected?: org.jenkins-ci.main:jenkins-core (Maven) ECOSYSTEM:introduced=0,fixed=2.138.4.
Is there a fix for CVE-2018-1000861?: Yes. org.jenkins-ci.main:jenkins-core (Maven): upgrade to 2.138.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2018-1000861 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2018-1000861?: Check whether you run Jenkins Stapler Web Framework or org.jenkins-ci.main:jenkins-core (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.138.4 or later

# set org.jenkins-ci.main:jenkins-core to 2.138.4 in your pom.xml or build.gradle

Affected products

Jenkins Jenkins 2.153 and earlier
Jenkins Jenkins LTS 2.138.3 and earlier
Jenkins Stapler all versions prior to fix

Identifiers

CVE-2018-1000861
GHSA-hhpm-5cp2-hg4x

Timeline

2018-12-05: advisory: Vendor security advisory published by Jenkins.
2018-12-10: disclosed: NVD Published Date.
2022-02-10: kev added: Added to CISA Known Exploited Vulnerabilities Catalog.

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