Description
Poll SCM Plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks. This allowed attackers to initiate polling of projects with a known name. While Jenkins in general does not consider polling to be a protection-worthy action as it's similar to cache invalidation, the plugin specifically adds a permission to be able to use this functionality, and this issue undermines that permission.
Remediation
References
https://jenkins.io/security/advisory/2017-07-10/
Related Vulnerabilities
CVE-2019-10432 Vulnerability in maven package org.jenkins-ci.plugins:htmlpublisher
CVE-2021-21603 Vulnerability in maven package org.jenkins-ci.main:jenkins-core
CVE-2011-5063 Vulnerability in maven package tomcat:catalina
CVE-2022-43427 Vulnerability in maven package com.compuware.jenkins:compuware-topaz-for-total-test
CVE-2023-25500 Vulnerability in maven package com.vaadin:flow-server