# CVE-2002-1647: Information disclosure in n/a

> Remote attackers can guess user passwords by reading the Referrer URL due to missing redirects on failed quick login attempts in Slash Slashcode.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Mar 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-34v4-g936-9pv9

## What is CVE-2002-1647?

CVE-2002-1647 is a medium-severity vulnerability in n/a, published on 28 Mar 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The quick login feature in Slash Slashcode does not redirect the user to an alternate URL when the wrong password is provided, which makes it easier for remote web sites to guess the proper passwords by reading the username and password from the Referrer URL.

## Which versions are affected by CVE-2002-1647?

It affects 1 product.


Products: Slashcode.com Slash.

## How do I fix CVE-2002-1647?

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

## Is CVE-2002-1647 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-2231](https://insights.sbomify.com/CVE-2008-2231/): SQL injection in n/a (high 7.5)
- [CVE-2008-2553](https://insights.sbomify.com/CVE-2008-2553/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1647 and fix it if it is affected.

What it is: CVE-2002-1647 is a medium-severity vulnerability in n/a, published on 28 Mar 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-1647 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-2002-1647/ (Markdown: https://insights.sbomify.com/CVE-2002-1647/index.md)
```

## Sources

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

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