Update dependency org.jsoup:jsoup to v1.15.3 [SECURITY] - #37
Closed
renovate[bot] wants to merge 1 commit into
Closed
Update dependency org.jsoup:jsoup to v1.15.3 [SECURITY]#37renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/maven-org.jsoup-jsoup-vulnerability
branch
from
April 17, 2023 13:06
7ecd701 to
b7f5cf2
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #37 +/- ##
============================================
+ Coverage 55.69% 56.05% +0.36%
- Complexity 282 288 +6
============================================
Files 93 95 +2
Lines 1273 1279 +6
Branches 66 66
============================================
+ Hits 709 717 +8
+ Misses 511 509 -2
Partials 53 53 ☔ View full report in Codecov by Sentry. |
renovate
Bot
force-pushed
the
renovate/maven-org.jsoup-jsoup-vulnerability
branch
2 times, most recently
from
September 22, 2023 13:34
75f446c to
ef1ef97
Compare
renovate
Bot
force-pushed
the
renovate/maven-org.jsoup-jsoup-vulnerability
branch
from
October 10, 2023 16:14
ef1ef97 to
4a606f1
Compare
renovate
Bot
force-pushed
the
renovate/maven-org.jsoup-jsoup-vulnerability
branch
from
February 27, 2024 10:22
4a606f1 to
445accf
Compare
renovate
Bot
force-pushed
the
renovate/maven-org.jsoup-jsoup-vulnerability
branch
3 times, most recently
from
May 2, 2024 12:56
017677e to
c5cea49
Compare
renovate
Bot
force-pushed
the
renovate/maven-org.jsoup-jsoup-vulnerability
branch
from
June 5, 2025 15:05
c5cea49 to
02da011
Compare
renovate
Bot
force-pushed
the
renovate/maven-org.jsoup-jsoup-vulnerability
branch
from
August 11, 2025 13:36
02da011 to
70e2594
Compare
renovate
Bot
force-pushed
the
renovate/maven-org.jsoup-jsoup-vulnerability
branch
from
September 3, 2025 11:53
70e2594 to
7f7a6d7
Compare
renovate
Bot
force-pushed
the
renovate/maven-org.jsoup-jsoup-vulnerability
branch
from
January 20, 2026 11:02
7f7a6d7 to
a54134c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.14.3→1.15.3GitHub Vulnerability Alerts
CVE-2022-36033
jsoup may incorrectly sanitize HTML including
javascript:URL expressions, which could allow cross-site scripting (XSS) attacks when a reader subsequently clicks that link. If the non-defaultSafeList.preserveRelativeLinksoption is enabled, HTML includingjavascript:URLs that have been crafted with control characters will not be sanitized. If the site that this HTML is published on does not set a Content Security Policy, an XSS attack is then possible.Impact
Sites that accept input HTML from users and use jsoup to sanitize that HTML, may be vulnerable to cross-site scripting (XSS) attacks, if they have enabled
SafeList.preserveRelativeLinksand do not set an appropriate Content Security Policy.Patches
This issue is patched in jsoup 1.15.3.
Users should upgrade to this version. Additionally, as the unsanitized input may have been persisted, old content should be cleaned again using the updated version.
Workarounds
To remediate this issue without immediately upgrading:
SafeList.preserveRelativeLinks, which will rewrite input URLs as absolute URLsBackground and root cause
jsoup includes a Cleaner component, which is designed to sanitize input HTML against configurable safe-lists of acceptable tags, attributes, and attribute values.
This includes removing potentially malicious attributes such as
<a href="javascript:...">, which may enable XSS attacks. It does this by validating URL attributes against allowed URL protocols (e.g.http,https).However, an attacker may be able to bypass this check by embedding control characters into the href attribute value. This causes the Java URL class, which is used to resolve relative URLs to absolute URLs before checking the URL's protocol, to treat the URL as a relative URL. It is then resolved into an absolute URL with the configured base URI.
For example,
java\tscript:...would resolve tohttps://example.com/java\tscript:....By default, when using a safe-list that allows
atags, jsoup will rewrite any relative URLs (e.g./foo/) to an absolute URL (e.g.https://example.com/foo/). Therefore, this attack attempt would be successfully mitigated. However, if the option SafeList.preserveRelativeLinks is enabled (which does not rewrite relative links to absolute), the input is left as-is.While Java will treat a path like
java\tscript:as a relative path, as it does not match the allowed characters of a URL spec, browsers may normalize out the control characters, and subsequently evaluate it as ajavascript:spec inline expression. That disparity then leads to an XSS opportunity.Sites defining a Content Security Policy that does not allow javascript expressions in link URLs will not be impacted, as the policy will prevent the script's execution.
For more information
If you have any questions or comments about this advisory:
Credits
Thanks to Jens Häderer, who reported this issue, and contributed to its resolution.
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.