CVE-2022-23106 is a medium-severity (CVSS 5.3) vulnerability in io.jenkins:configuration-as-code. A fix is available for io.jenkins:configuration-as-code — see the affected versions and patch details below.
Observable Discrepancy and Observable Timing Discrepancy in Jenkins Configuration as Code Plugin
EPSS Exploitation Probability
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.
How urgent is this, really
CVE-2022-23106 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
io.jenkins:configuration-as-code☕io.jenkins:configuration-as-code☕io.jenkins:configuration-as-code☕io.jenkins:configuration-as-codeReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.jenkins:configuration-as-code | ≥ 1.55&&< 1.55.1 | 1.55.1io.jenkins:configuration-as-code:1.55.1 |
| ☕Maven | io.jenkins:configuration-as-code | ≥ 1.54&&< 1.54.1 | 1.54.1io.jenkins:configuration-as-code:1.54.1 |
| ☕Maven | io.jenkins:configuration-as-code | ≥ 1.48&&< 1.53.1 | 1.53.1io.jenkins:configuration-as-code:1.53.1 |
| ☕Maven | io.jenkins:configuration-as-code | all versions | 1.47.1io.jenkins:configuration-as-code:1.47.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins:configuration-as-code, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-23106 can be triaged on real exposure rather than presence alone.
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
Is CVE-2022-23106 in your dependencies?
O3 Security finds CVE-2022-23106 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.