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

Issue metadata

Status: Verified
Owner: ----
Closed: Oct 11
Cc:
Type: Bug-Security



Sign in to add a comment

postgis: Heap-buffer-overflow in ptarray_from_wkb_state

Project Member Reported by ClusterFuzz-External, Jul 12 2017 Back to list

Issue description

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

Project: postgis
Fuzzer: libFuzzer_postgis_wkb_import_fuzzer
Fuzz target binary: wkb_import_fuzzer
Job Type: libfuzzer_asan_postgis
Platform Id: linux

Crash Type: Heap-buffer-overflow WRITE 8
Crash Address: 0x6030000000e0
Crash State:
  ptarray_from_wkb_state
  lwcircstring_from_wkb_state
  lwgeom_from_wkb_state
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

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


Issue filed automatically.

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

This bug is subject to a 90 day disclosure deadline. If 90 days elapse
without an upstream patch, then the bug report will automatically
become visible to the public.

When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any stable releases.
  * add any other useful information.
This information can help downstream consumers.

If you have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues.
 
Project Member

Comment 1 by ClusterFuzz-External, Jul 12 2017

Labels: OS-Linux
Project Member

Comment 2 by ClusterFuzz-External, Jul 13 2017

Cc: mate...@loskot.net
Project Member

Comment 3 by ClusterFuzz-External, Sep 5 2017

Labels: ReleaseBlock-Stable ClusterFuzz-Top-Crash
Testcase 6439724333924352 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 4 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 5 by sheriffbot@chromium.org, Oct 3

Labels: Deadline-Approaching
This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted.

- Your friendly Sheriffbot
Project Member

Comment 6 by sheriffbot@chromium.org, Oct 10

Labels: -restrict-view-commit -deadline-approaching Deadline-Exceeded
This bug has exceeded our disclosure deadline. It has been opened to the public.

- Your friendly Sheriffbot
Project Member

Comment 7 by ClusterFuzz-External, Oct 11

ClusterFuzz has detected this issue as fixed in range 201710100449:201710110449.

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

Project: postgis
Fuzzer: libFuzzer_postgis_wkb_import_fuzzer
Fuzz target binary: wkb_import_fuzzer
Job Type: libfuzzer_asan_postgis
Platform Id: linux

Crash Type: Heap-buffer-overflow WRITE 8
Crash Address: 0x6030000000e0
Crash State:
  ptarray_from_wkb_state
  lwcircstring_from_wkb_state
  lwgeom_from_wkb_state
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_postgis&range=201710100449:201710110449

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

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 8 by ClusterFuzz-External, Oct 11

Labels: ClusterFuzz-Verified
Status: Verified
ClusterFuzz testcase 6439724333924352 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

Sign in to add a comment