CVE-2022-43412 json
Non-constant time webhook token comparison in Jenkins Generic Webhook Trigger Plugin
published 2022-10-19 4 y ago modified 2026-06-17 4 mo ago also GHSA-2jxx-2x93-2q2f , EUVD-2022-6991
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
Jenkins Generic Webhook Trigger Plugin 1.84.1 and earlier uses a non-constant time comparison function when checking whether the provided and expected webhook token are equal, potentially allowing attackers to use statistical methods to obtain a valid webhook token.
Patch / fix
- maven org.jenkins-ci.plugins:generic-webhook-trigger 1.84.2
- jenkins generic_webhook_trigger 1.84.2
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:generic-webhook-trigger | <1.84.2 |
1.84.2 |
Affected products
- Jenkins project Jenkins Generic Webhook Trigger Plugin
Classification
References
-
jenkins.io
/security/advisory/2022-10-19/#SECURITY-2874
web, vendor-advisory
-
openwall.com
/lists/oss-security/2022/10/19/3
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-43412
advisory
-
github.com
/jenkinsci/generic-webhook-trigger-plugin
package
Sources
- CVE List CVE-2022-43412
- GitHub Advisory GHSA-2jxx-2x93-2q2f
- NVD CVE-2022-43412
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.