The FreeType Project - Bugs: bug #56587, Direct-leak (OSS-Fuzz 12809)
You are not allowed to post comments on this tracker with your current authentication level.
bug #56587: Direct-leak (OSS-Fuzz 12809)
Submitter: | Dirk Lemstra <dlemstra> | ||
Submitted: | Sun 07 Jul 2019 01:36:29 PM UTC | ||
Severity: | 3 - Normal | Item Group: | Incorrect behaviour |
Status: | Fixed | Privacy: | Public |
Assigned to: | wl | Open/Closed: | Closed |
Planned Release: | 2.10.2 |
Sun 14 Jul 2019 04:34:20 PM UTC, comment #3: |
Armin <cherusker> |
Fri 12 Jul 2019 09:37:30 AM UTC, comment #2: Should be fixed now in git. Please test. |
Werner LEMBERG <wl> |
Fri 12 Jul 2019 09:06:54 AM UTC, comment #1: Thanks for the report. Armin, could you add woff support to your fuzzing stuff? It seems that I can't reproduce the leak with `driver-asan-ubsan-o0-fttrace-ccache'. In case you can, please tell me how to do so.
|
Werner LEMBERG <wl> |
Sun 07 Jul 2019 01:36:29 PM UTC, original submission:
The ImageMagick project is using https://github.com/google/oss-fuzz to find bugs in our own library and in libraries that we use. The fuzzer found an issue and we think this is an issue that should be resolved in the library that we use. This issue is posted under the url https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12809. Below are the details of the issue that can be reproduced using the following technique: https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md.
|
Dirk Lemstra <dlemstra> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 7 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-07-12 | wl | Status | None | Fixed | |
Privacy | Private | Public | |||
Open/Closed | Open | Closed | |||
Planned Release | None | 2.10.2 | |||
2019-07-12 | wl | Assigned to | None | wl | |
2019-07-12 | wl | Carbon-Copy | - | Added cherusker | |
2019-07-07 | dlemstra | Attached File | - | Added clusterfuzz-testcase-minimized-ping_ttf_fuzzer-5647364126146560, #47169 |
Powered by Savane 3.13-d3ae.
Corresponding source code
Generally, `sfwoff.c' is pretty well fuzzed from a coverage perspective, not much we can do here but hope for interesting fuzzing input I'm afraid.
Obviously, we could split the TrueType target to work on WOFF files separately to generate more focussed input ... that could be worth a try?
As for `driver-asan-ubsan-o0-fttrace-ccache' -- Dirk, I understand that `clusterfuzz-testcase-minimized-ping_ttf_fuzzer-5647364126146560' is some blob that contains a WOFF font somewhere deep inside ... if my assumption is correct, is there an easy way to extract the WOFF from the blob?
Thanks
Armin