CVE-2024-35313 Other in n/a
High 7.3
Published
Updated
Check this codebase for CVE-2024-35313 and fix it if it is affected.
What it is: CVE-2024-35313 is a high-severity vulnerability in n/a, published on 17 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-35313 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2024-35313/ (Markdown: https://insights.sbomify.com/CVE-2024-35313/index.md)
Tor Arti circuits may incorrectly use full vanguards, potentially weakening anonymity guarantees for users relying on this library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-35313?
CVE-2024-35313 is a high-severity vulnerability in n/a, published on 17 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
In Tor Arti before 1.2.3, circuits sometimes incorrectly have a length of 3 (with full vanguards), aka TROVE-2024-004.
Weakness: CWE-130
Which versions are affected by CVE-2024-35313?
How do I fix CVE-2024-35313?
Upgrade to a fixed version.
Is CVE-2024-35313 being exploited?
There is no known exploitation of CVE-2024-35313 in the wild and no public exploit code.