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

> An attacker with low privileges can retrieve usernames and plaintext passwords from the administrative web interface of the email filter.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-23xp-397m-q9rx

## What is CVE-2002-1530?

CVE-2002-1530 is a medium-severity vulnerability in n/a, published on 1 Sep 2004. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The administrative web interface (STEMWADM) for SurfControl SuperScout Email Filter allows users to obtain usernames and plaintext passwords via a request to the userlist.asp program, which includes the passwords in a user editing form.

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

It affects 1 product.


Products: Surfcontrol Superscout Email Filter.

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

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

## Is CVE-2002-1530 being exploited?

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

Public exploit code:

- SurfControl SuperScout Email Filter 3.5 - User Credential Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-2121](https://insights.sbomify.com/CVE-2002-2121/): Denial of service in n/a (medium 5.0)
- [CVE-2002-1531](https://insights.sbomify.com/CVE-2002-1531/): Denial of service in n/a (medium 5.0)
- [CVE-2002-1532](https://insights.sbomify.com/CVE-2002-1532/): Denial of service in n/a (medium 5.0)
- [CVE-2002-1529](https://insights.sbomify.com/CVE-2002-1529/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1530 is a medium-severity vulnerability in n/a, published on 1 Sep 2004. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1530 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-2002-1530/ (Markdown: https://insights.sbomify.com/CVE-2002-1530/index.md)
```

## Sources

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

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