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

> Remote attackers can identify internal network IP addresses via CONNECT request error messages in Secure Webserver.

- **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:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-h8j3-gq64-h6q7

## What is CVE-2002-1535?

CVE-2002-1535 is a medium-severity vulnerability in n/a, published on 18 Mar 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Secure Webserver 1.1 in Raptor 6.5 and Symantec Enterprise Firewall 6.5.2 allows remote attackers to identify IP addresses of hosts on the internal network via a CONNECT request, which generates different error messages if the host is present.

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

It affects 2 products.


Products: Symantec Enterprise Firewall, Symantec Raptor Firewall.

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

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

## Is CVE-2002-1535 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4422](https://insights.sbomify.com/CVE-2007-4422/): Information disclosure in n/a (critical 9.3)
- [CVE-2005-3768](https://insights.sbomify.com/CVE-2005-3768/): Memory corruption in n/a (high 7.5)
- [CVE-2002-1463](https://insights.sbomify.com/CVE-2002-1463/): Other in n/a (high 7.5)
- [CVE-2002-0538](https://insights.sbomify.com/CVE-2002-0538/): Server-side request forgery in n/a (high 7.5)
- [CVE-2003-0106](https://insights.sbomify.com/CVE-2003-0106/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1535 is a medium-severity vulnerability in n/a, published on 18 Mar 2003. 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-2002-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-2002-1535/ (Markdown: https://insights.sbomify.com/CVE-2002-1535/index.md)
```

## Sources

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

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