Use-of-uninitialized-value in bool blink::FastParseColorInternal<unsigned char> |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5054769474568192 Fuzzer: libFuzzer_css_parser_fast_paths_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: bool blink::FastParseColorInternal<unsigned char> blink::CSSParserFastPaths::ParseColor blink::CSSParserFastPaths::MaybeParseValue Sanitizer: memory (MSAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=521690:521711 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5054769474568192 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Dec 6 2017
,
Dec 6 2017
Setting to Security_Severity-Low, as I don't think would be useful to an attacker as anything more than a single-byte compare.
,
Dec 6 2017
,
Dec 6 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7a5ddbe0167e6c988e8f0a4a4314ee8377cd21a4 commit 7a5ddbe0167e6c988e8f0a4a4314ee8377cd21a4 Author: Eric Willigers <ericwilligers@chromium.org> Date: Wed Dec 06 21:41:04 2017 CSS rgb(a) parsing: avoid uninitialized-value We check that the input has at least 5 characters before reading characters[4]. An rgb(a) color contains at least 3 numbers or percentages, plus separator characters, so the length of a valid rgb(a) color will be well over 5. TBR=nainar@chromium.org BUG= 792306 Change-Id: Iceb49992ee7c5da346e2f64cbc7ccb82ad619f81 Reviewed-on: https://chromium-review.googlesource.com/811784 Reviewed-by: Eric Willigers <ericwilligers@chromium.org> Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Cr-Commit-Position: refs/heads/master@{#522203} [modify] https://crrev.com/7a5ddbe0167e6c988e8f0a4a4314ee8377cd21a4/third_party/WebKit/Source/core/css/parser/CSSParserFastPaths.cpp
,
Dec 7 2017
ClusterFuzz has detected this issue as fixed in range 522181:522219. Detailed report: https://clusterfuzz.com/testcase?key=5054769474568192 Fuzzer: libFuzzer_css_parser_fast_paths_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: bool blink::FastParseColorInternal<unsigned char> blink::CSSParserFastPaths::ParseColor blink::CSSParserFastPaths::MaybeParseValue Sanitizer: memory (MSAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=521690:521711 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=522181:522219 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5054769474568192 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Dec 7 2017
ClusterFuzz testcase 5054769474568192 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Dec 7 2017
,
Mar 15 2018
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by elawrence@chromium.org
, Dec 6 2017Components: Blink>CSS
Labels: OS-Android OS-Chrome OS-Mac OS-Windows
Owner: ericwilligers@chromium.org