Groovy Postbuild Plugin up to 2.3.1 on Jenkins Persistent cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Groovy Postbuild Plugin up to 2.3.1 on Jenkins and classified as problematic. This affects an unknown part. Performing a manipulation results in cross site scripting (Persistent). This vulnerability is cataloged as CVE-2018-1000202. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability classified as problematic has been found in Groovy Postbuild Plugin up to 2.3.1 on Jenkins (Jenkins Plugin). This affects an unknown part. The manipulation with an unknown input leads to a cross site scripting vulnerability (Persistent). CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:
A persisted cross-site scripting vulnerability exists in Jenkins Groovy Postbuild Plugin 2.3.1 and older in various Jelly files that allows attackers able to control build badge content to define JavaScript that would be executed in another user's browser when that other user performs some UI actions.
The bug was discovered 05/09/2018. The weakness was shared 06/05/2018 (Website). The advisory is shared at jenkins.io. This vulnerability is uniquely identified as CVE-2018-1000202 since 06/05/2018. It is possible to initiate the attack remotely. A authentication is necessary for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 27 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 13416 (Jenkins Multiple Security Vulnerabilities (Jenkins Security Advisory 2018-05-09)).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-118982, VDB-118983, VDB-118984 and VDB-118985 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: PersistentClass: Cross site scripting / Persistent
CWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/09/2018 🔍06/05/2018 🔍
06/05/2018 🔍
06/05/2018 🔍
06/06/2018 🔍
07/16/2020 🔍
Sources
Advisory: jenkins.ioStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2018-1000202 (🔍)
GCVE (CVE): GCVE-0-2018-1000202
GCVE (VulDB): GCVE-100-118989
See also: 🔍
Entry
Created: 06/06/2018 10:21Updated: 07/16/2020 20:58
Changes: 06/06/2018 10:21 (60), 07/16/2020 20:58 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.