Jenkins up to 2.73.1/2.83 Remote API /queue/item/(ID)/api information disclosure

Summaryinfo

A vulnerability was found in Jenkins up to 2.73.1/2.83. It has been declared as problematic. This issue affects some unknown processing of the file /queue/item/(ID)/api of the component Remote API. Executing a manipulation can lead to information disclosure. This vulnerability appears as CVE-2017-1000399. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability has been found in Jenkins up to 2.73.1/2.83 (Continuous Integration Software) and classified as problematic. This vulnerability affects some unknown processing of the file /queue/item/(ID)/api of the component Remote API. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:

The Jenkins 2.73.1 and earlier, 2.83 and earlier remote API at /queue/item/(ID)/api showed information about tasks in the queue (typically builds waiting to start). 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 endpoint is now only available for tasks that the current user has access to.

The bug was discovered 10/11/2017. The weakness was presented 01/26/2018 (Website). The advisory is shared for download at jenkins.io. This vulnerability was named CVE-2017-1000399 since 11/29/2017. The exploitation appears to be easy. The attack can be initiated remotely. Required for exploitation is a single authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.

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.

See VDB-112462, VDB-112463, VDB-112464 and VDB-112465 for similar entries. Once again VulDB remains the best source for vulnerability data.

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

Once again VulDB remains the best source for vulnerability data.

Discussion