New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 2661 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Mar 2018
Cc:
Type: Bug



Sign in to add a comment

gdal: Direct-leak in CPLMalloc

Project Member Reported by ClusterFuzz-External, Jul 16 2017

Issue description

Detailed report: https://oss-fuzz.com/testcase?key=6193236899004416

Project: gdal
Fuzzer: libFuzzer_gdal_ogr_filesystem_fuzzer
Fuzz target binary: ogr_filesystem_fuzzer
Job Type: gdal_experimental
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  CPLMalloc
  CPLStrdup
  NASHandler::startElement
  
Sanitizer: address (ASAN)

Regressed: https://oss-fuzz.com/revisions?job=gdal_experimental&range=201705181644:201705211646

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6193236899004416


Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information.
 
Project Member

Comment 1 by ClusterFuzz-External, Jul 16 2017

Labels: OS-Linux
Project Member

Comment 2 by ClusterFuzz-External, Sep 5 2017

Labels: ReleaseBlock-Stable ClusterFuzz-Top-Crash
Testcase 6193236899004416 is a top crash on ClusterFuzz for linux platform. Marking this crash as a stable release blocker. If this is incorrect, remove the ReleaseBlock label.
Project Member

Comment 3 by aarya@google.com, Sep 5 2017

Labels: -ReleaseBlock-Stable
ReleaseBlock label don't apply to OSS-Fuzz, only to Chromium issue tracker.

However this is a top crash for your project, so please prioritize fixing this.
Project Member

Comment 4 by ClusterFuzz-External, Feb 9 2018

Labels: Fuzz-Blocker
This crash occurs very frequently on linux platform and is likely preventing the fuzzer ogr_filesystem_fuzzer from making much progress. Fixing this will allow more bugs to be found.

If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new
Project Member

Comment 5 by aarya@google.com, Feb 9 2018

Labels: -ClusterFuzz-Top-Crash
Project Member

Comment 6 by aarya@google.com, Mar 17 2018

Cc: mate...@loskot.net atho...@thinkspatial.com.au juergen....@gmail.com even.rou...@gmail.com ari.jo...@gmail.com schw...@gmail.com bishop....@gmail.com
Project Member

Comment 8 by ClusterFuzz-External, Mar 18 2018

ClusterFuzz has detected this issue as fixed in range 201803170607:201803180610.

Detailed report: https://oss-fuzz.com/testcase?key=6193236899004416

Project: gdal
Fuzzer: libFuzzer_gdal_ogr_filesystem_fuzzer
Fuzz target binary: ogr_filesystem_fuzzer
Job Type: gdal_experimental
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  CPLMalloc
  CPLStrdup
  NASHandler::startElement
  
Sanitizer: address (ASAN)

Regressed: https://oss-fuzz.com/revisions?job=gdal_experimental&range=201705181644:201705211646
Fixed: https://oss-fuzz.com/revisions?job=gdal_experimental&range=201803170607:201803180610

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6193236899004416

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 9 by ClusterFuzz-External, Mar 18 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: New)
ClusterFuzz testcase 6193236899004416 is verified as fixed, so closing issue as verified.

If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new
Project Member

Comment 10 by sheriffbot@chromium.org, Apr 17 2018

Labels: -restrict-view-commit
This bug has been fixed for 30 days. It has been opened to the public.

- Your friendly Sheriffbot

Sign in to add a comment