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

> Local attackers can decrypt all user passwords by exploiting a hardcoded symmetric key in the Sambar Server binary.

- **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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wwvp-6w6m-5m73

## What is CVE-2001-1106?

CVE-2001-1106 is a high-severity vulnerability in n/a, published on 2 Apr 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The default configuration of Sambar Server 5 and earlier uses a symmetric key that is compiled into the binary program for encrypting passwords, which could allow local users to break all user passwords by cracking the key or modifying a copy of the sambar program to call the decryption procedure.

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

It affects 1 product.


Products: Sambar Sambar Server.

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

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

## Is CVE-2001-1106 being exploited?

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

Public exploit code:

- Sambar Server 4.x/5.0 - Insecure Default Password Protection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0509](https://insights.sbomify.com/CVE-2000-0509/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-1286](https://insights.sbomify.com/CVE-2003-1286/): Server-side request forgery in n/a (high 7.5)
- [CVE-2002-0128](https://insights.sbomify.com/CVE-2002-0128/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1292](https://insights.sbomify.com/CVE-2001-1292/): Memory corruption in n/a (high 7.5)
- [CVE-1999-1523](https://insights.sbomify.com/CVE-1999-1523/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1106 is a high-severity vulnerability in n/a, published on 2 Apr 2003. 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-1106 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-1106/ (Markdown: https://insights.sbomify.com/CVE-2001-1106/index.md)
```

## Sources

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

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