How severe is GHSA-pw4g-jcp5-63m9?

GHSA-pw4g-jcp5-63m9 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-pw4g-jcp5-63m9?

GHSA-pw4g-jcp5-63m9 affects the following packages: org.jenkins-ci.plugins:rpmsign-plugin (Maven). Ecosystems affected: Maven.

How do I fix GHSA-pw4g-jcp5-63m9?

Update org.jenkins-ci.plugins:rpmsign-plugin to 0.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pw4g-jcp5-63m9 is resolved across your whole dependency graph.

How do I detect GHSA-pw4g-jcp5-63m9 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:rpmsign-plugin. 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-pw4g-jcp5-63m9 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-pw4g-jcp5-63m9?

O3 pinpoints whether GHSA-pw4g-jcp5-63m9 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-pw4g-jcp5-63m9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pw4g-jcp5-63m9 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.

What type of vulnerability is GHSA-pw4g-jcp5-63m9?

GHSA-pw4g-jcp5-63m9 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-pw4g-jcp5-63m9 published, and has it been updated?

GHSA-pw4g-jcp5-63m9 was published on July 28, 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-pw4g-jcp5-63m9

MEDIUM

GHSA-pw4g-jcp5-63m9 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in org.jenkins-ci.plugins:rpmsign-plugin. O3 Security confirms whether GHSA-pw4g-jcp5-63m9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Jenkins rpmsign-plugin does not perform a permission check in a method implementing form validation

Also known asCVE-2022-36893

Published

Jul 28, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

☕org.jenkins-ci.plugins:rpmsign-plugin

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

Jenkins rpmsign-plugin Plugin 0.5.0 and earlier does not perform a permission check in a method implementing form validation.

This allows attackers with Item/Read permission but without Item/Workspace or Item/Configure permission to check whether attacker-specified file patterns match workspace contents. A sequence of requests can be used to effectively list workspace contents.

rpmsign-plugin Plugin 0.5.1 requires Item/Workspace permission to validate patterns with workspace contents.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:rpmsign-plugin`	all versions	0.5.1

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:rpmsign-plugin. 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:rpmsign-plugin to 0.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pw4g-jcp5-63m9 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-pw4g-jcp5-63m9 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-pw4g-jcp5-63m9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Jenkins rpmsign-plugin Plugin 0.5.0 and earlier does not perform a permission check in a method implementing form validation. This allows attackers with Item/Read permission but without Item/Workspace or Item/Configure permission to check whether attacker-specified file patterns match workspace contents. A sequence of requests can be used to effectively list workspace contents. rpmsign-plugin Plugin 0.5.1 requires Item/Workspace permission to validate patterns with workspace contents.

O3 Security · Impact-Aware SCA

Is GHSA-pw4g-jcp5-63m9 in your dependencies?

O3 detects GHSA-pw4g-jcp5-63m9 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