Static Analysis Utilities Plugin up to 1.95 on Jenkins Permission DefaultGraphConfigurationView#doSave permission

Summaryinfo

A vulnerability identified as critical has been detected in Static Analysis Utilities Plugin up to 1.95 on Jenkins. This affects the function DefaultGraphConfigurationView#doSave of the component Permission. The manipulation leads to permission. This vulnerability is listed as CVE-2019-10308. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in Static Analysis Utilities Plugin up to 1.95 on Jenkins (Jenkins Plugin) and classified as critical. This issue affects the function DefaultGraphConfigurationView#doSave of the component Permission. The manipulation with an unknown input leads to a permission vulnerability. Using CWE to declare the problem leads to CWE-275. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

A missing permission check in Jenkins Static Analysis Utilities Plugin 1.95 and earlier in the DefaultGraphConfigurationView#doSave form handler method allowed attackers with Overall/Read permission to change the per-job default graph configuration for all users.

The bug was discovered 04/30/2019. The weakness was presented 04/30/2019 (oss-sec). The advisory is shared at openwall.com. The identification of this vulnerability is CVE-2019-10308 since 03/29/2019. The attack may be initiated remotely. A simple authentication is required for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1222 for this issue.

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

See VDB-134212, VDB-134214, VDB-134215 and VDB-134216 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Jenkins Plugin

Name

• Static Analysis Utilities Plugin

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.24
• 1.25
• 1.26
• 1.27
• 1.28
• 1.29
• 1.30
• 1.31
• 1.32
• 1.33
• 1.34
• 1.35
• 1.36
• 1.37
• 1.38
• 1.39
• 1.40
• 1.41
• 1.42
• 1.43
• 1.44
• 1.45
• 1.46
• 1.47
• 1.48
• 1.49
• 1.50
• 1.51
• 1.52
• 1.53
• 1.54
• 1.55
• 1.56
• 1.57
• 1.58
• 1.59
• 1.60
• 1.61
• 1.62
• 1.63
• 1.64
• 1.65
• 1.66
• 1.67
• 1.68
• 1.69
• 1.70
• 1.71
• 1.72
• 1.73
• 1.74
• 1.75
• 1.76
• 1.77
• 1.78
• 1.79
• 1.80
• 1.81
• 1.82
• 1.83
• 1.84
• 1.85
• 1.86
• 1.87
• 1.88
• 1.89
• 1.90
• 1.91
• 1.92
• 1.93
• 1.94
• 1.95

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