CVE-2005-1751 Race condition in n/a
Low 3.7
Published
Updated
Check this codebase for CVE-2005-1751 and fix it if it is affected.
What it is: CVE-2005-1751 is a low-severity vulnerability in n/a, published on 25 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-1751 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-2005-1751/ (Markdown: https://insights.sbomify.com/CVE-2005-1751/index.md)
Local attackers can exploit a race condition in shtool to create or modify arbitrary files via symlink attacks on temporary files.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2005-1751?
CVE-2005-1751 is a low-severity vulnerability in n/a, published on 25 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Race condition in shtool 2.0.1 and earlier allows local users to create or modify arbitrary files via a symlink attack on the .shtool.$$ temporary file, a different vulnerability than CVE-2005-1759.
Which versions are affected by CVE-2005-1751?
It affects 1 product.
Products include Shtool Shtool.
How do I fix CVE-2005-1751?
Upgrade to a fixed version.
Is CVE-2005-1751 being exploited?
There is no known exploitation of CVE-2005-1751 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as DEBIAN-CVE-2005-1751, GHSA-hpg8-96hf-f678.