CVE-2005-2948 Race condition in n/a
Low 2.1
Published
Updated
Check this codebase for CVE-2005-2948 and fix it if it is affected.
What it is: CVE-2005-2948 is a low-severity vulnerability in n/a, published on 16 Sep 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-2948 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-2948/ (Markdown: https://insights.sbomify.com/CVE-2005-2948/index.md)
Local attackers can bypass process kill restrictions by launching multiple processes simultaneously, evading termination by KillProcess.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2005-2948?
CVE-2005-2948 is a low-severity vulnerability in n/a, published on 16 Sep 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
KillProcess 2.20 and earlier allows local users to bypass kill list restrictions by launching multiple processes at the same time, which are not all killed by KillProcess.
Which versions are affected by CVE-2005-2948?
How do I fix CVE-2005-2948?
No fix has been published for CVE-2005-2948 yet. Limit exposure of the affected software until one is available.
Is CVE-2005-2948 being exploited?
There is no known exploitation of CVE-2005-2948 in the wild and no public exploit code.
Sources
Also known as GHSA-593c-jpx2-v8m8.