# CVE-2005-1993: Race condition in n/a

> Local attackers can exploit a race condition in sudo to gain elevated privileges via symlink attacks when specific sudoers configurations are used.

- **Severity:** Low 3.7 (`AV:L/AC:H/Au:N/C:P/I:P/A:P`)
- **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:** Yes
- **Published:** 20 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-1993, DSA-735-1, DSA-735-2, GHSA-8q3v-p32x-2pq7, RHSA-2005:535

## What is CVE-2005-1993?

CVE-2005-1993 is a low-severity vulnerability in n/a, published on 20 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Race condition in sudo 1.3.1 up to 1.6.8p8, when the ALL pseudo-command is used after a user entry in the sudoers file, allows local users to gain privileges via a symlink attack.

## Which versions are affected by CVE-2005-1993?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sudo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.6.7p5-1.1 |
| `sudo-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.6.7p5-1.1 |
| `sudo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.6.7p5-1.1 |
| `sudo-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.6.7p5-1.1 |
| `sudo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.6.7p5-1.1 |
| `sudo-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.6.7p5-1.1 |
| `sudo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.6.7p5-1.1 |
| `sudo-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.6.7p5-1.1 |
| `sudo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.6.7p5-30.1.1 |
| `sudo-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.6.7p5-30.1.1 |
| `sudo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.6.7p5-30.1.1 |
| `sudo-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.6.7p5-30.1.1 |
| `sudo` | Red Hat:enterprise_linux:4::es | All versions | 0:1.6.7p5-30.1.1 |
| `sudo-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:1.6.7p5-30.1.1 |
| `sudo` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.6.7p5-30.1.1 |
| `sudo-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.6.7p5-30.1.1 |

Products: Todd Miller Sudo.

## How do I fix CVE-2005-1993?

Apply the vendor's patch.

## Is CVE-2005-1993 being exploited?

There is no known exploitation of CVE-2005-1993 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2005-1831](https://insights.sbomify.com/CVE-2005-1831/): Privilege escalation in n/a (high 8.4)
- [CVE-2012-2337](https://insights.sbomify.com/CVE-2012-2337/): Privilege escalation in n/a (high 7.2)
- [CVE-2012-0809](https://insights.sbomify.com/CVE-2012-0809/): Memory corruption in n/a (high 7.2)
- [CVE-2006-0151](https://insights.sbomify.com/CVE-2006-0151/): Privilege escalation in n/a (high 7.2)
- [CVE-2002-0043](https://insights.sbomify.com/CVE-2002-0043/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1993 and fix it if it is affected.

What it is: CVE-2005-1993 is a low-severity vulnerability in n/a, published on 20 Jun 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-1993 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-1993/ (Markdown: https://insights.sbomify.com/CVE-2005-1993/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-1993
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-1993
- OSV: https://osv.dev/vulnerability/CVE-2005-1993

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-1993/
Summaries are generated and may contain mistakes; the official description above is the record.