New issue
Advanced search Search tips

Issue 816381 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Use-of-uninitialized-value in rsvg_property_bag_new

Project Member Reported by ClusterFuzz, Feb 26 2018

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=4628897598275584

Fuzzer: inferno_twister_c
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  rsvg_property_bag_new
  rsvg_start_element
  xmlParseStartTag
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=535692:535694

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4628897598275584

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Feb 26 2018

Labels: M-66
Project Member

Comment 2 by sheriffbot@chromium.org, Feb 26 2018

Labels: ReleaseBlock-Stable
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 3 by sheriffbot@chromium.org, Feb 26 2018

Labels: Pri-1
The listed regression range includes two HTML files for a test, and rev'ing the clang version number.

From the stack, this looks like one of those unreproducible flakes in GTK code.


Comment 5 by kenrb@chromium.org, Mar 1 2018

Cc: infe...@chromium.org
Abhishek, is there anything that we can do with this besides close it?

Comment 6 by kenrb@chromium.org, Mar 1 2018

Hmm, issue 817742 has the same regression range, and is marked as reproducible. I guess that these are somehow a consequence of the Clang roll?

Comment 7 by kenrb@chromium.org, Mar 2 2018

Owner: och...@chromium.org
Status: Assigned (was: Untriaged)
ochang@: Is this the same as issue 817742? It has a different stack but gives the same regression range, and is also a use-of-initialized-value in GTK.
Issue 818141 is a similar case: GTK, different stack, same range, reproducible.
Status: WontFix (was: Assigned)
This should no longer occur.
Project Member

Comment 10 by sheriffbot@chromium.org, Mar 27 2018

Labels: -Security_Impact-Head Security_Impact-Beta
Project Member

Comment 11 by sheriffbot@chromium.org, Jun 11 2018

Labels: -Restrict-View-SecurityTeam allpublic
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