GHSA-rvh4-g2rj-hr9c
HIGHGHSA-rvh4-g2rj-hr9c is a high-severity (CVSS 8.1) Path Traversal vulnerability in io.jenkins.plugins:warnings-ng. O3 Security confirms whether GHSA-rvh4-g2rj-hr9c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Path Traversal in Jenkins Warnings Next Generation Plugin
Real-World Exposure
io.jenkins.plugins:warnings-ng☕io.jenkins.plugins:warnings-ng☕io.jenkins.plugins:warnings-ng☕io.jenkins.plugins:warnings-ngReal-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
Jenkins Warnings Next Generation Plugin prior to 9.10.3, 9.7.1, 9.5.2, and 9.0.2 does not restrict the name of a file when configuring a custom ID.
This allows attackers with Item/Configure permission to write and read specific files with a hard-coded suffix on the Jenkins controller file system.
Jenkins Warnings Next Generation Plugin 9.10.3, 9.7.1, 9.5.2, and 9.0.2 checks for the presence of prohibited directory separator characters in the custom ID.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.jenkins.plugins:warnings-ng | ≥ 9.8.0&&< 9.10.3 | 9.10.3 |
| ☕Maven | io.jenkins.plugins:warnings-ng | ≥ 9.6.0&&< 9.7.1 | 9.7.1 |
| ☕Maven | io.jenkins.plugins:warnings-ng | ≥ 9.1.0&&< 9.5.2 | 9.5.2 |
| ☕Maven | io.jenkins.plugins:warnings-ng | all versions | 9.0.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:warnings-ng. 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.
Fix
Update io.jenkins.plugins:warnings-ng to 9.10.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rvh4-g2rj-hr9c is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 pinpoints whether GHSA-rvh4-g2rj-hr9c 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-rvh4-g2rj-hr9c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-rvh4-g2rj-hr9c in your dependencies?
O3 detects GHSA-rvh4-g2rj-hr9c across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.