Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-rp4x-xpgf-4xv7

HIGH

GHSA-rp4x-xpgf-4xv7 is a high-severity (CVSS 7.1) Cross-Site Request Forgery (CSRF) vulnerability in org.jenkins-ci.plugins:selenium. O3 Security confirms whether GHSA-rp4x-xpgf-4xv7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Complete lack of CSRF protection in Jenkins Selenium Plugin can lead to OS command injection

Also known asCVE-2020-2196
Published
May 24, 2022
Updated
Nov 8, 2023
Affected
1 pkg
Patched
None yet
Exploits
None indexed

Blast Radius

1 pkg affected
org.jenkins-ci.plugins:selenium

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Selenium Plugin 3.141.59 and earlier has no CSRF protection for its HTTP endpoints.

This allows attackers to perform the following actions:

  • Restart the Selenium Grid hub.
  • Delete or replace the plugin configuration.
  • Start, stop, or restart Selenium configurations on specific nodes.

Through carefully chosen configuration parameters, these actions can result in OS command injection on the Jenkins controller.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
Mavenorg.jenkins-ci.plugins:seleniumall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:selenium. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of org.jenkins-ci.plugins:selenium has shipped for GHSA-rp4x-xpgf-4xv7 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-rp4x-xpgf-4xv7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rp4x-xpgf-4xv7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Selenium Plugin 3.141.59 and earlier has no CSRF protection for its HTTP endpoints. This allows attackers to perform the following actions: - Restart the Selenium Grid hub. - Delete or replace the plugin configuration. - Start, stop, or restart Selenium configurations on specific nodes. Through carefully chosen configuration parameters, these actions can result in OS command injection on the Jenkins controller.
O3 Security · Impact-Aware SCA

Is GHSA-rp4x-xpgf-4xv7 in your dependencies?

O3 detects GHSA-rp4x-xpgf-4xv7 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.