OWASP / java-html-sanitizer

93%

master: 94%

LAST BUILD ON BRANCH 5372c747173f312b9342fac2ea6bc7445d3abeee

branch: SELECT

CHANGE BRANCH

x

• No branch selected
• 5372c747173f312b9342fac2ea6bc7445d3abeee
• OBRAZKI-1029
• dependabot/maven/parent/com.google.guava-guava-29.0-jre
• dependabot/maven/parent/junit-junit-4.13.1
• main
• master
• mikesamuel-patch-1
• obscure-named-char-refs-need-semis
• release-20190325.1
• release-20190503.1
• release-20190610.1
• release-20191001.1
• release-20200615.1
• release-20200713.1
• sgjg-non-character-handling
• svg-mathml-mixed-case-names

Build # #133

Build Type

push

Committed by web-flow

Commit Message

Decode attribute content differently from text node content (#255)

As described in issue #254 `&para` is a full complete character
reference when decoding text node content, but not when
decoding attribute content which causes problems for URL attribute
values like

    /test?param1=foo&param2=bar

As shown via JS test code in that issue, a small set of
next characters prevent a character reference name match
from being considered complete.

This commit:
- modifies the decode functions to take an extra parameter
  `boolean inAttribute`, and modifies the Trie traversal
  loops to not store a longest match so far based on that
  parameter and some next character tests
- modifies the HTML lexer to pass that attribute appropriately
- for backwards compat, leaves the old APIs in place but `@deprecated`
- adds unit tests for the decode functions
- adds a unit test for the specific input from the issue

This change should make us more conformant with observed
browser behaviour so is not expected to cause compatibility
problems for existing users.

Fixes #254

Coverage Stats

14 of 16 new or added lines in 3 files covered. (87.5%)

3945 of 4252 relevant lines covered (92.78%)

0.93 hits per line