Skip to content

Crafted input may cause the jsoup HTML and XML parser to get stuck, timeout, or throw unchecked exceptions

High
jhy published GHSA-m72m-mhq2-9p6c Aug 18, 2021

Package

maven org.jsoup:jsoup (Maven)

Affected versions

< 1.14.2

Patched versions

1.14.2

Description

Impact

What kind of vulnerability is it? Who is impacted?
Those using jsoup to parse untrusted HTML or XML may be vulnerable to DOS attacks. If the parser is run on user supplied input, an attacker may supply content that causes the parser to get stuck (loop indefinitely until cancelled), to complete more slowly than usual, or to throw an unexpected exception. This effect may support a denial of service attack.

Patches

Has the problem been patched? What versions should users upgrade to?
Users should upgrade to jsoup 1.14.2

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?
Users may rate limit input parsing. Users should limit the size of inputs based on system resources. Users should implement thread watchdogs to cap and timeout parse runtimes.

References

Are there any links users can visit to find out more?
https://jsoup.org/news/release-1.14.2
https://jsoup.org/news/release-1.14.1

These impacting inputs were found through the use of the Jazzer JVM Fuzzer, running in the OSS-Fuzz project.
OSS-Fuzz Integration of jsoup was done by Roman Wagner from Code Intelligence.

For more information

If you have any questions or comments about this advisory:

  • Open a discussion issue in jsoup

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
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:N/UI:N/S:U/C:N/I:N/A:H

CVE ID

CVE-2021-37714

Weaknesses

No CWEs

Credits