Skip to content

jQuery UI vulnerable to XSS when refreshing a checkboxradio with an HTML-like initial text label

Moderate severity GitHub Reviewed Published Jul 15, 2022 in jquery/jquery-ui • Updated Sep 26, 2023

Package

nuget jQuery.UI.Combined (NuGet)

Affected versions

< 1.13.2

Patched versions

1.13.2
npm jquery-ui (npm)
< 1.13.2
1.13.2
bundler jquery-ui-rails (RubyGems)
< 7.0.0
7.0.0
maven org.webjars.npm:jquery-ui (Maven)
< 1.13.2
1.13.2

Description

Impact

Initializing a checkboxradio widget on an input enclosed within a label makes that parent label contents considered as the input label. If you call .checkboxradio( "refresh" ) on such a widget and the initial HTML contained encoded HTML entities, they will erroneously get decoded. This can lead to potentially executing JavaScript code.

For example, starting with the following initial secure HTML:

<label>
	<input id="test-input">
	&lt;img src=x onerror="alert(1)"&gt;
</label>

and calling:

$( "#test-input" ).checkboxradio();
$( "#test-input" ).checkboxradio( "refresh" );

will turn the initial HTML into:

<label>
	<!-- some jQuery UI elements -->
	<input id="test-input">
	<img src=x onerror="alert(1)">
</label>

and the alert will get executed.

Patches

The bug has been patched in jQuery UI 1.13.2.

Workarounds

To remediate the issue, if you can change the initial HTML, you can wrap all the non-input contents of the label in a span:

<label>
	<input id="test-input">
	<span>&lt;img src=x onerror="alert(1)"&gt;</span>
</label>

References

https://blog.jqueryui.com/2022/07/jquery-ui-1-13-2-released/

For more information

If you have any questions or comments about this advisory, search for a relevant issue in the jQuery UI repo. If you don't find an answer, open a new issue.

References

@mgol mgol published to jquery/jquery-ui Jul 15, 2022
Published to the GitHub Advisory Database Jul 18, 2022
Reviewed Jul 18, 2022
Published by the National Vulnerability Database Jul 20, 2022
Last updated Sep 26, 2023

Severity

Moderate

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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:N/UI:R/S:C/C:L/I:L/A:N

EPSS score

0.222%
(61st percentile)

Weaknesses

CVE ID

CVE-2022-31160

GHSA ID

GHSA-h6gj-6jjq-h8g9

Source code

Credits

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