Closed Bug 1465440 Opened 6 years ago Closed 5 years ago

Disable CRC checks in FlacDemuxer for FUZZING

Categories

(Core :: Audio/Video: Playback, enhancement, P3)

Unspecified
Linux
enhancement

Tracking

()

RESOLVED FIXED
mozilla70
Tracking Status
firefox-esr60 --- wontfix
firefox-esr68 --- wontfix
firefox62 --- wontfix
firefox68 --- wontfix
firefox69 --- wontfix
firefox70 --- fixed

People

(Reporter: decoder, Assigned: decoder)

References

Details

(Keywords: sec-other, sec-want, Whiteboard: [post-critsmash-triage][adv-main70-])

Attachments

(1 file)

The FlacDemuxer has some CRC8/CRC16 header checks that we should probably disable in FUZZING builds.
can't the fuzzer simply set the CRC value?

it's not that much required. Especially if you know the existing CRC and are only changing a byte at the time. The new CRC can be easily calculated from there
No, the fuzzer cannot do that. In order to do so, the fuzzer (in this case libfuzzer) would have to know the file structure and it doesn't know that.
let's fix libfuzzer then :D
(In reply to Jean-Yves Avenard [:jya] from comment #3)
> let's fix libfuzzer then :D

It is the whole point of libFuzzer not being required to know the target file format structure. There is nothing to fix here on the fuzzer side, it is common practice to fix this in the target code.
Priority: -- → P3
Component: Audio/Video → Audio/Video: Playback

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:decoder, could you have a look please?
For more information, please visit auto_nag documentation.

Flags: needinfo?(choller)
Flags: qe-verify+
Whiteboard: [post-critsmash-triage]
Flags: qe-verify+ → qe-verify-
Whiteboard: [post-critsmash-triage] → [post-critsmash-triage][adv-main70-]
Group: core-security-release
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: