CVE-2005-1853 Privilege escalation in n/a
High 7.2
Published
Updated
Check this codebase for CVE-2005-1853 and fix it if it is affected.
What it is: CVE-2005-1853 is a high-severity vulnerability in n/a, published on 3 Aug 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-1853 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-1853/ (Markdown: https://insights.sbomify.com/CVE-2005-1853/index.md)
Local attackers can exploit insecure temporary file creation in the Gopher client to escalate privileges on the system.
- 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-1853?
CVE-2005-1853 is a high-severity vulnerability in n/a, published on 3 Aug 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
gopher.c in the Gopher client 3.0.5 does not properly create temporary files, which allows local users to gain privileges.
Which versions are affected by CVE-2005-1853?
It affects 1 product.
Products include University of Minnesota Gopher.
How do I fix CVE-2005-1853?
Apply the vendor's patch.
Is CVE-2005-1853 being exploited?
There is no known exploitation of CVE-2005-1853 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as DEBIAN-CVE-2005-1853, DSA-770-1, GHSA-3823-wj6r-jpc9.