Skip to content
Fencer Vulns
medium 4.3

CVE-2022-20613 json

Cross-Site Request Forgery in Jenkins Mailer Plugin

published 2022-01-12 4 y ago modified 2026-06-17 4 mo ago also GHSA-85rq-hp8x-ghjq , EUVD-2022-0518

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits
0
none known

Summary

A cross-site request forgery (CSRF) vulnerability in Jenkins Mailer Plugin 391.ve4a_38c1b_cf4b_ and earlier allows attackers to use the DNS used by the Jenkins instance to resolve an attacker-specified hostname.

Patch / fix

  • maven org.jenkins-ci.plugins:mailer 1.34.2, 408.vd726a
  • Jenkins project Jenkins Mailer Plugin 1.34.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-20613 updated cvss 4.3

jenkins-2-plugins/mailer: form validation method does not require POST requests which could lead to CSRF

  • Red Hat OpenShift Container Platform 3.11 jenkins, jenkins-2-plugins
    affected: no fix available, no fix planned “Will not fix”
  • Red Hat OpenShift Container Platform 4 jenkins, jenkins-2-plugins
    affected: no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins:mailer
>=391.ve4a38c1bcf4b, <408.vd726a
<1.34.2
408.vd726a
1.34.2

Affected products

  • Jenkins project Jenkins Mailer Plugin

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

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.