Jenkins up to 2.73.1/2.83 Remote API /job/(job-name)/api permission

Summaryinfo

A vulnerability was found in Jenkins up to 2.73.1/2.83. It has been rated as problematic. Impacted is an unknown function of the file /job/(job-name)/api of the component Remote API. The manipulation leads to permission. This vulnerability is traded as CVE-2017-1000400. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Jenkins up to 2.73.1/2.83 (Continuous Integration Software) and classified as problematic. This issue affects an unknown function of the file /job/(job-name)/api of the component Remote API. The manipulation with an unknown input leads to a permission vulnerability. Using CWE to declare the problem leads to CWE-275. Impacted is confidentiality. The summary by CVE is:

The Jenkins 2.73.1 and earlier, 2.83 and earlier remote API at /job/(job-name)/api contained information about upstream and downstream projects. This included information about tasks that the current user otherwise has no access to, e.g. due to lack of Item/Read permission. This has been fixed, and the API now only lists upstream and downstream projects that the current user has access to.

The bug was discovered 10/11/2017. The weakness was shared 01/26/2018 (Website). The advisory is shared at jenkins.io. The identification of this vulnerability is CVE-2017-1000400 since 11/29/2017. The exploitation is known to be easy. The attack may be initiated remotely. The successful exploitation requires a simple authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1222 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 106 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-112462, VDB-112463, VDB-112464 and VDB-112465 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Continuous Integration Software

Name

• Jenkins

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17
• 2.18
• 2.19
• 2.20
• 2.21
• 2.22
• 2.23
• 2.24
• 2.25
• 2.26
• 2.27
• 2.28
• 2.29
• 2.30
• 2.31
• 2.32
• 2.33
• 2.34
• 2.35
• 2.36
• 2.37
• 2.38
• 2.39
• 2.40
• 2.41
• 2.42
• 2.43
• 2.44
• 2.45
• 2.46
• 2.47
• 2.48
• 2.49
• 2.50
• 2.51
• 2.52
• 2.53
• 2.54
• 2.55
• 2.56
• 2.57
• 2.58
• 2.59
• 2.60
• 2.61
• 2.62
• 2.63
• 2.64
• 2.65
• 2.66
• 2.67
• 2.68
• 2.69
• 2.70
• 2.71
• 2.72
• 2.73
• 2.73.0
• 2.73.1
• 2.74
• 2.75
• 2.76
• 2.77
• 2.78
• 2.79
• 2.80
• 2.81
• 2.82
• 2.83

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion