harfbuzz:hb-subset-fuzzer: Heap-buffer-overflow in OT::HintingDevice* hb_serialize_context_t::embed<OT::HintingDevice>

2020-01-18T18:11:42
ID OSSFUZZ-20211
Type ossfuzz
Reporter Google
Modified 2020-02-23T20:00:11

Description

Project: https://github.com/harfbuzz/harfbuzz.git

Detailed Report: https://oss-fuzz.com/testcase?key=5206191479455744

Project: harfbuzz Fuzzing Engine: libFuzzer Fuzz Target: hb-subset-fuzzer Job Type: libfuzzer_asan_i386_harfbuzz Platform Id: linux

Crash Type: Heap-buffer-overflow READ {} Crash Address: 0xf250370a Crash State: OT::HintingDevice hb_serialize_context_t::embed<OT::HintingDevice> OT::HintingDevice::copy OT::Device::copy

Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_i386_harfbuzz&range=202001150211:202001160356

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

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored.

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.