# CVE-2002-1484: Server-side request forgery in n/a

> Remote attackers can use the DB4Web server as a proxy to scan ports on other systems when verbose debug messages are enabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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-fc65-58v2-9r8h

## What is CVE-2002-1484?

CVE-2002-1484 is a critical server-side request forgery 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

DB4Web server, when configured to use verbose debug messages, allows remote attackers to use DB4Web as a proxy and attempt TCP connections to other systems (port scan) via a request for a URL that specifies the target IP address and port, which produces a connection status in the resulting error message.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Siemens Db4web.

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

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

## Is CVE-2002-1484 being exploited?

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

Public exploit code:

- DB4Web 3.4/3.6 - Connection Proxy (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1484 is a critical server-side request forgery 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1484 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-1484/ (Markdown: https://insights.sbomify.com/CVE-2002-1484/index.md)
```

## Sources

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

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