How severe is CVE-2022-23106?

CVE-2022-23106 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 CVE-2022-23106?

CVE-2022-23106 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 CVE-2022-23106?

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 CVE-2022-23106 is resolved across your whole dependency graph.

How do I detect CVE-2022-23106 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 CVE-2022-23106 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 CVE-2022-23106?

O3 pinpoints whether CVE-2022-23106 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 CVE-2022-23106 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-23106 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 CVE-2022-23106?

CVE-2022-23106 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 CVE-2022-23106 published, and has it been updated?

CVE-2022-23106 was published on January 12, 2022 and was last updated on July 9, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2022-23106

MEDIUM

CVE-2022-23106 is a medium-severity (CVSS 5.3) CWE-203 vulnerability in io.jenkins:configuration-as-code. O3 Security confirms whether CVE-2022-23106 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asGHSA-fpj7-9xm6-8hgr

Published

Jan 12, 2022

Updated

Jul 9, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Real-World Exposure

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 1.55 and earlier used a non-constant time comparison function when validating an authentication token allowing attackers to use statistical methods to obtain a valid authentication token.

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 CVE-2022-23106 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 CVE-2022-23106 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 CVE-2022-23106. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-23106 in your dependencies?

O3 detects CVE-2022-23106 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