How severe is GHSA-gqm2-2gcx-p88w?

GHSA-gqm2-2gcx-p88w 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-gqm2-2gcx-p88w?

GHSA-gqm2-2gcx-p88w affects the following packages: org.jenkins-ci.plugins:credentials-binding (Maven), org.jenkins-ci.plugins:credentials-binding (Maven). Ecosystems affected: Maven.

How do I fix GHSA-gqm2-2gcx-p88w?

Update org.jenkins-ci.plugins:credentials-binding to 1.27.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gqm2-2gcx-p88w is resolved across your whole dependency graph.

How do I detect GHSA-gqm2-2gcx-p88w in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:credentials-binding. 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-gqm2-2gcx-p88w 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-gqm2-2gcx-p88w?

O3 pinpoints whether GHSA-gqm2-2gcx-p88w 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-gqm2-2gcx-p88w actively exploited in the wild?

No public exploit code has been indexed for GHSA-gqm2-2gcx-p88w 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-gqm2-2gcx-p88w?

GHSA-gqm2-2gcx-p88w 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-gqm2-2gcx-p88w published, and has it been updated?

GHSA-gqm2-2gcx-p88w was published on January 13, 2022 and was last updated on July 3, 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-gqm2-2gcx-p88w

MEDIUM

GHSA-gqm2-2gcx-p88w is a medium-severity (CVSS 4.3) CWE-862 vulnerability in org.jenkins-ci.plugins:credentials-binding. O3 Security confirms whether GHSA-gqm2-2gcx-p88w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Incorrect Permission Assignment for Critical Resource in Jenkins Credentials Binding Plugin

Also known asCVE-2022-20616

Published

Jan 13, 2022

Updated

Jul 3, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

☕org.jenkins-ci.plugins:credentials-binding☕org.jenkins-ci.plugins:credentials-binding

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 Credentials Binding Plugin prior to 1.27.1 and 1.24.1 does not perform a permission check in a method implementing form validation.

This allows attackers with Overall/Read access to validate if a credential ID refers to a secret file credential and whether it’s a zip file.

Credentials Binding Plugin 1.27.1 and 1.24.1 performs permission checks when validating secret file credentials IDs.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:credentials-binding`	≥ 1.25&&< 1.27.1	1.27.1
☕Maven	`org.jenkins-ci.plugins:credentials-binding`	all versions	1.24.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:credentials-binding. 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:credentials-binding to 1.27.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gqm2-2gcx-p88w 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-gqm2-2gcx-p88w 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-gqm2-2gcx-p88w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Jenkins Credentials Binding Plugin prior to 1.27.1 and 1.24.1 does not perform a permission check in a method implementing form validation. This allows attackers with Overall/Read access to validate if a credential ID refers to a secret file credential and whether it’s a zip file. Credentials Binding Plugin 1.27.1 and 1.24.1 performs permission checks when validating secret file credentials IDs.

O3 Security · Impact-Aware SCA

Is GHSA-gqm2-2gcx-p88w in your dependencies?

O3 detects GHSA-gqm2-2gcx-p88w 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