Jenkins Poll SCM Plugin Request cross-site request forgery

Summaryinfo

A vulnerability was found in Jenkins. It has been rated as problematic. This impacts an unknown function of the component Poll SCM Plugin. Performing a manipulation as part of Request results in cross-site request forgery. This vulnerability is reported as CVE-2017-1000093. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Jenkins (Continuous Integration Software) (version unknown). It has been classified as problematic. This affects an unknown function of the component Poll SCM Plugin. The manipulation as part of a Request leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. The summary by CVE is:

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.

The bug was discovered 07/10/2017. The weakness was disclosed 10/05/2017 (Website). The advisory is shared at jenkins.io. This vulnerability is uniquely identified as CVE-2017-1000093 since 07/13/2017. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 86 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-107448, VDB-107449, VDB-107450 and VDB-107451 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Continuous Integration Software

Name

• Jenkins

License

• open-source

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion