# CVE-2001-1169: Auth bypass in n/a

> An attacker with local user access can initialize S/Key sequences without authentication, enabling privilege escalation via sudo or other S/Key-dependent services.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hxfh-gjpx-m797

## What is CVE-2001-1169?

CVE-2001-1169 is a high-severity authentication bypass vulnerability in n/a, published on 15 Mar 2002. 

### Official description

keyinit in S/Key does not require authentication to initialize a one-time password sequence, which allows an attacker who has gained privileges to a user account to create new one-time passwords for use in other activities that may use S/Key authentication, such as sudo.

## Which versions are affected by CVE-2001-1169?

It affects 1 product.


Products: Bell Communications Research S Key.

## How do I fix CVE-2001-1169?

No fix has been published for CVE-2001-1169 yet. Limit exposure of the affected software until one is available.

## Is CVE-2001-1169 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1169 and fix it if it is affected.

What it is: CVE-2001-1169 is a high-severity authentication bypass vulnerability in n/a, published on 15 Mar 2002. 
Exploitation: There is no known exploitation of CVE-2001-1169 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-2001-1169/ (Markdown: https://insights.sbomify.com/CVE-2001-1169/index.md)
```

## Sources

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

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