How severe is CVE-2024-35313?

CVE-2024-35313 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.

Is CVE-2024-35313 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (21st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2024-35313?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2024-35313 have an EU (EUVD) identifier?

Yes. CVE-2024-35313 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-1571.

When was CVE-2024-35313 published?

CVE-2024-35313 was published on 2024-05-17 and last updated on 2026-06-17.

CVE-2024-35313

CVE-2024-35313 is a high-severity vulnerability with a CVSS 3.x base score of 7.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-130.

Key facts

Severity: High (CVSS 3.x base score 7.3)
EPSS exploit prediction: 0% (21st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-1571
Weakness: CWE-130
Published: 2024-05-17
Last modified: 2026-06-17

Description

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

Frequently asked questions

What is 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.
How severe is CVE-2024-35313?: CVE-2024-35313 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.
Is CVE-2024-35313 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (21st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2024-35313?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-35313 have an EU (EUVD) identifier?: Yes. CVE-2024-35313 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-1571.
When was CVE-2024-35313 published?: CVE-2024-35313 was published on 2024-05-17 and last updated on 2026-06-17.

References

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

Other CWE-130 vulnerabilities

CVE-2022-2714 — Critical (CVSS 9.8): Improper Handling of Length Parameter Inconsistency in GitHub repository francoisjacquet/rosariosis prior to 10.0.
CVE-2026-18397 — Critical (CVSS 9.4): This vulnerability enables unauthenticated remote code execution (RCE) on a victim's machine by exploiting a…
CVE-2026-9054 — Critical (CVSS 9.2): An attacker sending tcp, il, rudp, rudp, or gre packets with a length less than the header size would trigger a kernel…
CVE-2026-5706 — High (CVSS 8.9): In Bluetooth Mesh SDK 6.1.4 and earlier, malformed extended advertisements can trigger out-of-bounds writes leading to…
CVE-2026-58096 — High (CVSS 8.8): LcpDecodeConfig() did not validate the length of received endpoint discriminator options against the minimum required…
CVE-2022-1543 — High (CVSS 8.8): Improper handling of Length parameter in GitHub repository erudika/scoold prior to 1.49.4. When the text size is large…

Browse all CWE-130 vulnerabilities →