Opened 3 years ago
Closed 2 years ago
#4996 closed defect (worksforme)
wkb_import_fuzzer: Stack-overflow in lwcurvepoly_from_wkb_state
Reported by: | komzpa | Owned by: | pramsey |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 3.1.7 |
Component: | postgis | Version: | 2.5.x -- EOL |
Keywords: | Cc: |
Description
Found via oss-fuzz
Attachments (1)
Change History (10)
by , 3 years ago
Attachment: | clusterfuzz-testcase-minimized-wkb_import_fuzzer-4510152078786560.fuzz added |
---|
comment:1 by , 3 years ago
Milestone: | PostGIS 3.2.0 → PostGIS 3.1.5 |
---|
comment:2 by , 3 years ago
comment:4 by , 3 years ago
Milestone: | PostGIS 3.1.5 → PostGIS 3.2.1 |
---|
comment:5 by , 3 years ago
Milestone: | PostGIS 3.2.1 → PostGIS 3.1.6 |
---|
comment:6 by , 2 years ago
Milestone: | PostGIS 3.1.6 → PostGIS 3.1.7 |
---|
comment:7 by , 2 years ago
Hm, saw a type wrapping issue in the usan builds but no stack overflow… https://github.com/postgis/postgis/pull/704
comment:9 by , 2 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
And what exactly do we do with this .fuzz file? the README.txt in the fuzzers directory has no steps. This is why I have no truck with ossfuzz, I'm always trying to figure out what the heck to do with the odd reporting artifacts.