Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Change issue status back to 'Assigned'
Pending code changes (auto-populated)
Planned date for disclosure [ID: 1349435]
OSS-Fuzz Project name [ID: 1349507]
Date reported to upstream maintainer [ID: 1349561]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
#1Project: speex
Fuzzing Engine: libFuzzer
Fuzz Target: speex_decode_fuzzer_fixed
Job Type: libfuzzer_ubsan_speex
Platform Id: linux
Crash Type: Divide-by-zero
Crash Address:
Crash State:
sb_decode
speex_decode
speexdec_fuzzer.cc
Sanitizer: undefined (UBSAN)
Regressed:
Reproducer Testcase:
Issue filed automatically.
See
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
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.