Opened 7 years ago
Last modified 3 years ago
#835 new defect
Google oss-fuzz
Reported by: | goatbar | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 3.11.0 |
Component: | Default | Version: | main |
Severity: | Unassigned | Keywords: | fuzzing ubsan asan msan |
Cc: |
Description
Please consider joining Google's OSS Fuzz project.
It would be great to get fuzzers that cover any input format (WKT, WKB, and ?) and if those succeed in parsing, try to write out the geometry and try out the geometry on a range of operations.
Example of a GEOS fuzzing target (could definitely be improved):
GDAL and Proj.4 are participating.
- https://trac.osgeo.org/gdal/ticket/6883
- https://trac.osgeo.org/gdal/browser/trunk/gdal/fuzzers
- http://lists.maptools.org/pipermail/proj/2017-May/thread.html
Configs:
- https://github.com/google/oss-fuzz/tree/master/projects/gdal
- https://github.com/google/oss-fuzz/tree/master/projects/proj4
Note that I'm one of the people getting GDAL OSS Fuzz notifications and an engineer at Google (on Earth Engine, not the teams building fuzzing and sanitizing tools)
Change History (2)
comment:1 by , 3 years ago
Milestone: | → 3.10.0 |
---|
comment:2 by , 3 years ago
Milestone: | 3.10.0 → 3.11.0 |
---|
Note:
See TracTickets
for help on using tickets.
Retargeting in prep for GEOS 3.10.0 release