Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #25251

Closed (moved)
(moved)
Open
Created Feb 14, 2018 by Nick Mathewson@nickm🍬

Fix TROVE-2018-004: bad consensus can trigger null pointer crash.

When checking their own versions against the subprotocol versions listed in a consensus document, Tor instances could be made to crash if the consensus was incorrectly formatted.

This is a low-severity bug, since it can only be exploited by corrupting a majority of directory authorities. (And any attacker who can do that, can do far worse.)

We're tracking this one as TROVE-2018-004. It was present in 0.2.9.4-alpha and later. It is fixed in 0.2.9.15, 0.3.1.10, 0.3.2.10, and 0.3.3.3-alpha.

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