Torproject

Tor

49 Schwachstellen gefunden.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS -
  • Veröffentlicht 20.08.2026 21:17:11
  • Zuletzt bearbeitet 20.08.2026 21:17:11

tor before 0.4.9.9 was prone to a NULL write after free when sending a CONFLUX_SWITCH cell fails. The return value of relay_send_command_from_edge() was ignored, so a send failure (which calls circuit_mark_for_close() and removes the leg via cfx_d...

  • EPSS -
  • Veröffentlicht 20.08.2026 21:15:49
  • Zuletzt bearbeitet 20.08.2026 22:18:06

tor before 0.4.9.9 was prone to an out-of-bounds write when parsing a consensus or detached signature with unexpected signature digest type. Impact is minor for most Tor roles, but potentially major for directory authorities. This is TROVE-2026-0...

  • EPSS -
  • Veröffentlicht 20.08.2026 21:02:36
  • Zuletzt bearbeitet 20.08.2026 21:17:11

tor before 0.4.9.9 was prone to an infinite loop when decompressing a truncated zlib/gzip stream with done=1. A truncated stream never reaches Z_STREAM_END, causing zlib to return Z_BUF_ERROR with no input remaining, which buf_add_compress() misto...

  • EPSS -
  • Veröffentlicht 20.08.2026 20:57:50
  • Zuletzt bearbeitet 20.08.2026 21:17:11

Tor before 0.4.9.9 was prone to a compression bomb bypass where an attacker could concatenate many gzip or zlib sub-streams, each just under the per-stream detection threshold, to avoid the compression bomb check entirely. This is TROVE-2026-022.

  • EPSS -
  • Veröffentlicht 20.08.2026 20:52:29
  • Zuletzt bearbeitet 20.08.2026 21:17:11

Tor before 0.4.9.11 is prone to a race condition where in just the right circumstances a rendezvous point could man-in-the-middle (impersonate) the onion service that the client was trying to reach.

  • EPSS -
  • Veröffentlicht 20.08.2026 20:47:39
  • Zuletzt bearbeitet 20.08.2026 21:17:10

Tor before 0.4.9.11 is prone to a use-after-free (and potential double free) of a conflux object when a recovery leg revives a conflux set whose last linked leg has already been closed. A malicious exit node could use this to crash a client. This is ...

  • EPSS -
  • Veröffentlicht 20.08.2026 20:38:42
  • Zuletzt bearbeitet 20.08.2026 21:17:10

Tor before 0.4.9.10 did not reject a CONFLUX_LINK cell that arrives on a circuit which already has attached streams. A malicious client could send a RELAY_COMMAND_BEGIN before the CONFLUX_LINK on the same circuit, attaching an exit stream that would ...

  • EPSS 0.34%
  • Veröffentlicht 07.05.2026 04:16:35
  • Zuletzt bearbeitet 07.05.2026 17:24:36

Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026-007.

  • EPSS 0.33%
  • Veröffentlicht 07.05.2026 04:16:35
  • Zuletzt bearbeitet 08.05.2026 17:06:51

Tor before 0.4.9.7 has a NULL pointer dereference when a CERT cell is received out of order, aka TROVE-2026-006.

  • EPSS 0.34%
  • Veröffentlicht 07.05.2026 04:16:35
  • Zuletzt bearbeitet 08.05.2026 17:07:19

Tor before 0.4.9.7, when circuit queue memory pressure exists, can experience a client crash because of a double close of a circuit, aka TROVE-2026-009.