CVE-2017-2607

MEDIUMCVSS 4.2/10EPSS 1.06%

Last modified

CVE-2017-2607 is a medium-severity vulnerability rated 4.2/10 on the CVSS scale. jenkins before versions 2.44, 2.32.2 is vulnerable to a persisted cross-site scripting vulnerability in console notes (SECURITY-382). Jenkins allows plugins to annotate build logs, adding new content or changing the presentation of existing content while the build is running. EPSS estimates a 1.06% chance of exploitation in the next 30 days.

Description

jenkins before versions 2.44, 2.32.2 is vulnerable to a persisted cross-site scripting vulnerability in console notes (SECURITY-382). Jenkins allows plugins to annotate build logs, adding new content or changing the presentation of existing content while the build is running. Malicious Jenkins users, or users with SCM access, could configure jobs or modify build scripts such that they print serialized console notes that perform cross-site scripting attacks on Jenkins users viewing the build logs.

Metrics

CVSS 3.0
4.2/10

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

EPSS Probability
1.06%

60.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
JenkinsJenkins< 2.44
JenkinsJenkins< 2.32.2

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-2607?
jenkins before versions 2.44, 2.32.2 is vulnerable to a persisted cross-site scripting vulnerability in console notes (SECURITY-382). Jenkins allows plugins to annotate build logs, adding new content or changing the presentation of existing content while the build is running. Malicious Jenkins users, or users with SCM access, could configure jobs or modify build scripts such that they print serialized console notes that perform cross-site scripting attacks on Jenkins users viewing the build logs.
How severe is CVE-2017-2607?
CVE-2017-2607 has a CVSS score of 4.2/10 (MEDIUM severity). The EPSS model estimates a 1.06% probability of exploitation in the next 30 days.
How do I fix CVE-2017-2607?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2017

Are you affected by CVE-2017-2607?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST