CVE-2020-2230

CVE-2020-2230: vulnerability in Jenkins

Published · Updated

Follow this CVE+ Monitor Jenkins+ Monitor org.jenkins-ci.main:jenkins-core

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

45Vexday Risk Score

No sign of exploitation. It has a public proof of concept.

ssvc Attendepss 83%
from disclosure to weapon121 days
Published on NVDAug 12
1st PoC+121d
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Red HatVEX document ↗
Fixed
4 products (9 components)
Red Hat OpenShift Container Platform 4.4 · Red Hat OpenShift Container Platform 3.11 · Red Hat OpenShift Container Platform 4.3 · Red Hat OpenShift Container Platform 4.5
fix ↗
Not affected
2 products (5 components) — because the vulnerable code is not present in the product
Red Hat OpenShift Container Platform 4.3 · Red Hat Fuse 7
Jenkins 2.251 and earlier, LTS 2.235.3 and earlier does not escape the project naming strategy description, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by users with Overall/Manage permission.
Affected products
Jenkins project · Jenkins
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Related CVEs — Jenkins

In the same product, most dangerous first.

CVE-2019-10405—CVE-2019-10405EPSS 65.3%CVE-2019-10352—CVE-2019-10352EPSS 10.0%CVE-2020-2103—CVE-2020-2103EPSS 7.0%CVE-2020-2229—CVE-2020-2229EPSS 6.8%CVE-2020-2231—CVE-2020-2231EPSS 5.3%CVE-2022-0538—CVE-2022-0538EPSS 3.9%