How severe is GHSA-fpj7-9xm6-8hgr?

GHSA-fpj7-9xm6-8hgr has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-fpj7-9xm6-8hgr?

GHSA-fpj7-9xm6-8hgr affects the following packages: io.jenkins:configuration-as-code (Maven), io.jenkins:configuration-as-code (Maven), io.jenkins:configuration-as-code (Maven), io.jenkins:configuration-as-code (Maven). Ecosystems affected: Maven.

How do I fix GHSA-fpj7-9xm6-8hgr?

Update io.jenkins:configuration-as-code to 1.55.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fpj7-9xm6-8hgr is resolved across your whole dependency graph.

How do I detect GHSA-fpj7-9xm6-8hgr in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins:configuration-as-code. 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-fpj7-9xm6-8hgr 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-fpj7-9xm6-8hgr?

O3 pinpoints whether GHSA-fpj7-9xm6-8hgr 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-fpj7-9xm6-8hgr actively exploited in the wild?

No public exploit code has been indexed for GHSA-fpj7-9xm6-8hgr 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 is the EPSS score for GHSA-fpj7-9xm6-8hgr?

GHSA-fpj7-9xm6-8hgr has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 62th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fpj7-9xm6-8hgr?

GHSA-fpj7-9xm6-8hgr is classified as CWE-203 (CWE-203). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-fpj7-9xm6-8hgr published, and has it been updated?

GHSA-fpj7-9xm6-8hgr was published on January 21, 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-fpj7-9xm6-8hgr

LOW

Observable Discrepancy and Observable Timing Discrepancy in Jenkins Configuration as Code Plugin

Also known asCVE-2022-23106

Published

Jan 21, 2022

Updated

Feb 16, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk62th percentile+1.03%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

☕io.jenkins:configuration-as-code☕io.jenkins:configuration-as-code☕io.jenkins:configuration-as-code☕io.jenkins:configuration-as-code

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 Configuration as Code Plugin prior to 1.55.1, 1.54.1, 1.53.1, and 1.47.1 does not use a constant-time comparison when checking whether two authentication tokens are equal.

This could potentially allow attackers to use statistical methods to obtain a valid authentication token.

Configuration as Code Plugin 1.55.1, 1.54.1, 1.53.1, and 1.47.1 now uses a constant-time comparison when validating authentication tokens.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.jenkins:configuration-as-code`	≥ 1.55&&< 1.55.1	1.55.1
☕Maven	`io.jenkins:configuration-as-code`	≥ 1.54&&< 1.54.1	1.54.1
☕Maven	`io.jenkins:configuration-as-code`	≥ 1.48&&< 1.53.1	1.53.1
☕Maven	`io.jenkins:configuration-as-code`	all versions	1.47.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins:configuration-as-code. 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:configuration-as-code to 1.55.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fpj7-9xm6-8hgr 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-fpj7-9xm6-8hgr 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-fpj7-9xm6-8hgr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Jenkins Configuration as Code Plugin prior to 1.55.1, 1.54.1, 1.53.1, and 1.47.1 does not use a constant-time comparison when checking whether two authentication tokens are equal. This could potentially allow attackers to use statistical methods to obtain a valid authentication token. Configuration as Code Plugin 1.55.1, 1.54.1, 1.53.1, and 1.47.1 now uses a constant-time comparison when validating authentication tokens.

O3 Security · Impact-Aware SCA

Is GHSA-fpj7-9xm6-8hgr in your dependencies?

O3 detects GHSA-fpj7-9xm6-8hgr 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