Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #24150
Closed (moved) (moved)
Open
Issue created Nov 05, 2017 by Nick Mathewson@nickm🌻

Memory leak in v3 hsdesc parsing with empty encrypted data.

When we get a v3 hsdesc where the decrypted part starts with a NUL byte, then decrypt_desc_layer will return 0, since the length of the output is 0. But "0" can also mean that there's an error in the decryption.

Found with OSS-fuzz.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking