How severe is GHSA-rpj6-2q8r-98f8?

GHSA-rpj6-2q8r-98f8 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-rpj6-2q8r-98f8?

GHSA-rpj6-2q8r-98f8 affects the following packages: org.jenkins-ci.plugins:audit-trail (Maven). Ecosystems affected: Maven.

How do I fix GHSA-rpj6-2q8r-98f8?

Update org.jenkins-ci.plugins:audit-trail to 3.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rpj6-2q8r-98f8 is resolved across your whole dependency graph.

How do I detect GHSA-rpj6-2q8r-98f8 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:audit-trail. 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.

How do I mitigate GHSA-rpj6-2q8r-98f8 if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-rpj6-2q8r-98f8?

O3 pinpoints whether GHSA-rpj6-2q8r-98f8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rpj6-2q8r-98f8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rpj6-2q8r-98f8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-rpj6-2q8r-98f8 published, and has it been updated?

GHSA-rpj6-2q8r-98f8 was published on February 10, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-rpj6-2q8r-98f8

MEDIUM

GHSA-rpj6-2q8r-98f8 is a medium-severity (CVSS 5.3) vulnerability in org.jenkins-ci.plugins:audit-trail. O3 Security confirms whether GHSA-rpj6-2q8r-98f8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Request logging bypass in Jenkins Audit Trail Plugin

Also known asCVE-2020-2287

Published

Feb 10, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

☕org.jenkins-ci.plugins:audit-trail

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

Audit Trail Plugin logs requests whose URL path matches an admin-configured regular expression.

A discrepancy between the behavior of the plugin and the Stapler web framework in parsing URL paths allows attackers to craft URLs that would bypass request logging in Audit Trail Plugin 3.6 and earlier. This only applies to Jenkins 2.227 and earlier, LTS 2.204.5 and earlier, as the fix for SECURITY-1774 prohibits dispatch of affected requests.

Audit Trail Plugin 3.7 processes request URL paths the same way as the Stapler web framework.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:audit-trail`	all versions	3.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:audit-trail. 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 org.jenkins-ci.plugins:audit-trail to 3.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rpj6-2q8r-98f8 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-rpj6-2q8r-98f8 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-rpj6-2q8r-98f8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Audit Trail Plugin logs requests whose URL path matches an admin-configured regular expression. A discrepancy between the behavior of the plugin and the Stapler web framework in parsing URL paths allows attackers to craft URLs that would bypass request logging in Audit Trail Plugin 3.6 and earlier. This only applies to Jenkins 2.227 and earlier, LTS 2.204.5 and earlier, as the fix for [SECURITY-1774](https://www.jenkins.io/security/advisory/2020-03-25/#SECURITY-1774) prohibits dispatch of affected requests. Audit Trail Plugin 3.7 processes request URL paths the same way as the Stapler web fr

O3 Security · Impact-Aware SCA

Is GHSA-rpj6-2q8r-98f8 in your dependencies?

O3 detects GHSA-rpj6-2q8r-98f8 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works