Jenkins Pipeline Maven Integration vulnerabilities

6 CVEs affecting Jenkins Pipeline Maven Integration, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2023-41934, published 2023-09-06.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

CVE-2019-10327, published 2019-05-31. High severity, CVSS 8.1. EPSS: 1.4% chance of exploitation in the next 30 days. An XML external entities (XXE) vulnerability in Jenkins Pipeline Maven Integration Plugin 1.7.0 and earlier allowed attackers able to control a temporary directory's content on the agent running the…
CVE-2020-2234, published 2020-08-12. Medium severity, CVSS 6.5. EPSS: 1.1% chance of exploitation in the next 30 days. A missing permission check in Jenkins Pipeline Maven Integration Plugin 3.8.2 and earlier allows users with Overall/Read access to connect to an attacker-specified JDBC URL using attacker-specified…
CVE-2020-2235, published 2020-08-12. Medium severity, CVSS 6.5. EPSS: 0.9% chance of exploitation in the next 30 days. A cross-site request forgery (CSRF) vulnerability in Jenkins Pipeline Maven Integration Plugin 3.8.2 and earlier allows attackers to connect to an attacker-specified JDBC URL using attacker-specified…
CVE-2020-2233, published 2020-08-12. Medium severity, CVSS 6.5. EPSS: 0.8% chance of exploitation in the next 30 days. A missing permission check in Jenkins Pipeline Maven Integration Plugin 3.8.2 and earlier allows users with Overall/Read access to enumerate credentials ID of credentials stored in Jenkins.
CVE-2020-2256, published 2020-09-16. Medium severity, CVSS 5.4. EPSS: 0.7% chance of exploitation in the next 30 days. Jenkins Pipeline Maven Integration Plugin 3.9.2 and earlier does not escape the upstream job's display name shown as part of a build cause, resulting in a stored cross-site scripting (XSS)…
CVE-2023-41934, published 2023-09-06. Medium severity, CVSS 5.3. EPSS: 0.7% chance of exploitation in the next 30 days. Jenkins Pipeline Maven Integration Plugin 1330.v18e473854496 and earlier does not properly mask (i.e., replace with asterisks) usernames of credentials specified in custom Maven settings in Pipeline…