Yes, I will update chromium with this as per https://cs.chromium.org/chromium/src/third_party/libxml/ chromium/roll.py On Thu, Nov 9, 2017 at 10:35 AM, Jungshik Shin (신정식, 申政湜) <jshin chromium org> wrote:Thank you, Joel and Nick !Joel: I guess you're gonna roll libxml in the Chromium tree to a version including these changes.Jungshik2017-11-08 15:22 GMT-08:00 Joel Hockey <joelhockey chromium org>:Thanks Nick. Nice work with the test.On Sun, Nov 5, 2017 at 2:04 AM, Nick Wellnhofer <wellnhofer aevum de> wrote:On 26/10/2017 03:17, Joel Hockey wrote:
I've updated the patch using git format-patch.
Thanks for the updated patch. Applied here: https://git.gnome.org/browse/libxml2/commit/?id=0b19f236a263 a7b0acacd4ea84dc7237303ee3d9
The original bug found by fuzzer only relates to UTF8 decoding, so using Shift-JIS or anything else wont help.
Why not? My reasoning was that ICU uses the same code path for all variable-width encodings. I simply converted your test file to EUC-JP and it turns out that this triggers the bug as well:
https://git.gnome.org/browse/libxml2/commit/?id=72182550926d 31ad17357bd3ed69e49d7e69df02
Nick
Attachment:
0001-Change-calls-to-xmlCharEncInput-to-set-flush-false-w.patch
Description: Text Data
Attachment:
icu_parse_test.utf8.xml
Description: XML document