# CVE-2002-1578: Misconfiguration in n/a

> Remote attackers can access sensitive SAP data by connecting directly to the unprotected Oracle database in default SAP R/3 installations.

- **Severity:** High 7.5 (`AV:N/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:** 16 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-gpm8-6j9v-6v7f

## What is CVE-2002-1578?

CVE-2002-1578 is a high-severity vulnerability in n/a, published on 16 Mar 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default installation of SAP R/3, when using Oracle and SQL*net V2 3.x, 4.x, and 6.10, allows remote attackers to obtain arbitrary, sensitive SAP data by directly connecting to the Oracle database and executing queries against the database, which is not password-protected.

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

It affects 1 product.


Products: Sap Sap R 3.

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

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

## Is CVE-2002-1578 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4815](https://insights.sbomify.com/CVE-2005-4815/): Command injection in n/a (high 7.5)
- [CVE-2002-1577](https://insights.sbomify.com/CVE-2002-1577/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2003-1035](https://insights.sbomify.com/CVE-2003-1035/): Auth bypass in n/a (high 7.5)
- [CVE-2005-1691](https://insights.sbomify.com/CVE-2005-1691/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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