Icescrum Jenkins Icescrum

Don't miss out!

Thousands of developers use stack.watch to stay informed.
Get an email whenever new security vulnerabilities are reported in Jenkins Icescrum.

By the Year

In 2025 there have been 0 vulnerabilities in Jenkins Icescrum. Last year, in 2024 Icescrum had 1 security vulnerability published. Right now, Icescrum is on track to have less security vulnerabilities in 2025 than it did last year.

Year Vulnerabilities Average Score
2025 0 0.00
2024 1 0.00
2023 0 0.00
2022 0 0.00
2021 0 0.00
2020 0 0.00
2019 3 5.80

It may take a day or so for new Icescrum vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Jenkins Icescrum Security Vulnerabilities

Jenkins iceScrum Plugin <1.1.6 XSS via unsanitized URLs
CVE-2024-28160 - March 06, 2024

Jenkins iceScrum Plugin 1.1.6 and earlier does not sanitize iceScrum project URLs on build views, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to configure jobs.

A cross-site request forgery vulnerability in Jenkins iceScrum Plugin 1.1.5 and earlier
CVE-2019-10441 4.3 - Medium - October 16, 2019

A cross-site request forgery vulnerability in Jenkins iceScrum Plugin 1.1.5 and earlier allowed attackers to connect to an attacker-specified URL using attacker-specified credentials.

Session Riding

A missing permission check in Jenkins iceScrum Plugin 1.1.5 and earlier
CVE-2019-10442 4.3 - Medium - October 16, 2019

A missing permission check in Jenkins iceScrum Plugin 1.1.5 and earlier allowed attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials.

AuthZ

Jenkins iceScrum Plugin 1.1.4 and earlier stored credentials unencrypted in job config.xml files on the Jenkins master where they could be viewed by users with Extended Read permission
CVE-2019-10443 8.8 - High - October 16, 2019

Jenkins iceScrum Plugin 1.1.4 and earlier stored credentials unencrypted in job config.xml files on the Jenkins master where they could be viewed by users with Extended Read permission, or access to the master file system.

Cleartext Storage of Sensitive Information

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Jenkins Icescrum or by Jenkins? Click the Watch button to subscribe.

Jenkins
Vendor

subscribe