Skip to content

Stored XSS vulnerability in Validating String Parameter Plugin

High severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Dec 7, 2023

Package

maven org.jenkins-ci.plugins:validating-string-parameter (Maven)

Affected versions

<= 2.4

Patched versions

2.5

Description

Validating String Parameter Plugin 2.4 and earlier does not escape regular expressions in tooltips. Additionally, Validating String Parameter Plugin 2.4 does not escape parameter names and parameter descriptions.

This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Job/Configure permission.

Validating String Parameter Plugin 2.5 escapes regular expressions in tooltips and parameter names. Parameter descriptions are rendered using the configured markup formatter.

References

Published by the National Vulnerability Database Sep 16, 2020
Published to the GitHub Advisory Database May 24, 2022
Reviewed Dec 29, 2022
Last updated Dec 7, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.050%
(22nd percentile)

Weaknesses

CVE ID

CVE-2020-2257

GHSA ID

GHSA-fvwh-wv43-8qj5

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.