# CVE-2001-1003: Weak cryptography in n/a

> Weak encryption in Respondus allows local attackers to decrypt stored credentials from the WEBCT.SVR file, leading to privilege escalation.

- **Severity:** Medium 4.6 (`AV:L/AC:L/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:** No
- **Published:** 2 Feb 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-g8jg-wcrf-374h

## What is CVE-2001-1003?

CVE-2001-1003 is a medium-severity vulnerability in n/a, published on 2 Feb 2002. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Respondus 1.1.2 for WebCT uses weak encryption to remember usernames and passwords, which allows local users who can read the WEBCT.SVR file to decrypt the passwords and gain additional privileges.

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

It affects 1 product.


Products: Webct Respondus.

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

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

## Is CVE-2001-1003 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-1003 exists.

Public exploit code:

- Respondus for WebCT 1.1.2 - Weak Password Encryption (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1003 is a medium-severity vulnerability in n/a, published on 2 Feb 2002. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-1003 exists.

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-1003/ (Markdown: https://insights.sbomify.com/CVE-2001-1003/index.md)
```

## Sources

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

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