Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Opus
Opus
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Xiph.Org
  • OpusOpus
  • Issues
  • #1980

Closed
Open
Opened Oct 10, 2013 by Mark Harris@markhDeveloper

opus_decode undefined behavior decoding FEC from invalid packet

Attempting to decode FEC from an invalid packet can cause the opus decoder to use uninitialized data from the stack, and potentially dereference out-of-bounds memory addresses or crash depending on the contents of the uninitialized data.

Decoding the attached opus_demo bitstream under valgrind demonstrates the issue.

opus_demo -d 48000 1 -inbandfec opus-fec-uninit.opusdemo out.pcm
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: xiph/opus#1980