CVE-2020-2196 Complete lack of CSRF protection in Jenkins Selenium Plugin can lead to OS command injection

High 8.0 Published Updated

Attackers can perform administrative actions on the Jenkins Selenium Plugin due to missing CSRF protection, requiring an upgrade to secure the endpoints.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2020-2196?

CVE-2020-2196 is a high-severity vulnerability in Jenkins Selenium Plugin, published on 3 Jun 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

Jenkins Selenium Plugin 3.141.59 and earlier has no CSRF protection for its HTTP endpoints, allowing attackers to perform all administrative actions provided by the plugin.

Weakness: CWE-352

Which versions are affected by CVE-2020-2196?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:selenium. It affects 1 product.

PackageAffectedFixed in
org.jenkins-ci.plugins:selenium MavenAll versions to 3.141.59None
org.jenkins-ci.plugins:selenium MavenAll versions to 3.141.59None

Products include Jenkins Selenium.

How do I fix CVE-2020-2196?

No fix has been published for CVE-2020-2196 yet. Limit exposure of the affected software until one is available.

Is CVE-2020-2196 being exploited?

There is no known exploitation of CVE-2020-2196 in the wild and no public exploit code.

Sources

Also known as GHSA-rp4x-xpgf-4xv7.

Is CVE-2020-2196 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free