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

> Weak random password generation in Slashcode allows attackers to brute force session IDs and gain unauthorized access to user accounts.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-573g-2667-xfj9

## What is CVE-2001-1535?

CVE-2001-1535 is a medium-severity vulnerability in n/a, published on 14 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Slashcode 2.0 creates new accounts with an 8-character random password, which could allow local users to obtain session ID's from cookies and gain unauthorized access via a brute force attack.

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

It affects 1 product.


Products: Open Source Development Network Slashcode.

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

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

## Is CVE-2001-1535 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-1015](https://insights.sbomify.com/CVE-2000-1015/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2002-1748](https://insights.sbomify.com/CVE-2002-1748/): Auth bypass in n/a (high 7.2)
- [CVE-2002-1681](https://insights.sbomify.com/CVE-2002-1681/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2004-2656](https://insights.sbomify.com/CVE-2004-2656/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2002-0292](https://insights.sbomify.com/CVE-2002-0292/): Cross-site scripting in n/a (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1535 is a medium-severity vulnerability in n/a, published on 14 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2001-1535 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-1535/ (Markdown: https://insights.sbomify.com/CVE-2001-1535/index.md)
```

## Sources

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

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