[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #22753 [Core Tor/Tor]: Resolve TROVE-2017-006: Regression in guard family avoidance in 0.3.0 series (was: Resolve TROVE-2017-006)
#22753: Resolve TROVE-2017-006: Regression in guard family avoidance in 0.3.0
series
-------------------------------------------------+-------------------------
Reporter: nickm | Owner:
Type: defect | Status: new
Priority: High | Milestone: Tor:
| 0.3.2.x-final
Component: Core Tor/Tor | Version:
Severity: Major | Resolution:
Keywords: 030-backport 031-backport tor- | Actual Points:
client guard-selection |
Parent ID: | Points: 1
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Changes (by nickm):
* priority: Medium => High
* points: => 1
* keywords: 030-backport 031-backport => 030-backport 031-backport tor-
client guard-selection
* severity: Normal => Major
Old description:
New description:
In 0.3.0, when I revised the guard selection code, I got the "don't use
your exit as first-hop if even if it's your guard" logic right, but I
accidentally omitted "don't use anything in the exit's family as a guard."
The impact here is that some circuits will still use a guard on the same
circuit as an exit even when the two are in the same family.
(Putting this issue up on the tracker now because knowing about it does
not (much) help an attacker exploit it.)
This is TROVE-2017-006 and CVE-2017-0377.
--
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22753#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs