Generic-webhook-trigger CVEs
3 CVEs, 1 protected by Waratek
Overview 3 matches · 1 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
1
33.3%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
2
66.7%
blocked by ARMR today
1
33.3%
partly blocked
0
0.0%
not blocked
2
66.7%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
3
100.0%
split by
peak 1 / month
Jun 211
Protected by Waratek1
Critical1
blocked by ARMR today1
No public exploit1
Jul 210
Aug 210
Sep 210
Oct 210
Nov 210
Dec 210
Jan 220
Feb 221
No exploit published1
Medium1
not blocked1
No public exploit1
Mar 220
Apr 220
May 220
Jun 220
Jul 220
Aug 220
Sep 220
Oct 221
No exploit published1
Medium1
not blocked1
No public exploit1
Jun 21Aug 21Oct 21Dec 21Feb 22Apr 22Jun 22Aug 22Oct 22
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-43412 | Medium | 2022-10-19 | No exploit published | No public exploit | 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. |
| CVE-2022-25185 | Medium | 2022-02-15 | No exploit published | No public exploit | Jenkins Generic Webhook Trigger Plugin 1.81 and earlier does not escape the build cause when using the webhook, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission. |
| CVE-2021-21669 | Critical | 2021-06-18 | Protected by Waratek | No public exploit | Jenkins Generic Webhook Trigger Plugin 1.72 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks. |