# CVE-2002-0571: Missing authorization in n/a

> Local users can access restricted data in Oracle9i database server by exploiting a flaw in ANSI outer join syntax handling.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-72r4-pqjh-3mc3

## What is CVE-2002-0571?

CVE-2002-0571 is a high-severity missing authorization vulnerability in Oracle Oracle9i, published on 2 Apr 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Oracle Oracle9i database server 9.0.1.x allows local users to access restricted data via a SQL query using ANSI outer join syntax.

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

It affects 1 product.


Products: Oracle Oracle9i.

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

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

## Is CVE-2002-0571 being exploited?

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

## Other vulnerabilities in Oracle Oracle9i

- [CVE-2003-1208](https://insights.sbomify.com/CVE-2003-1208/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-1264](https://insights.sbomify.com/CVE-2002-1264/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0965](https://insights.sbomify.com/CVE-2002-0965/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0509](https://insights.sbomify.com/CVE-2002-0509/): Denial of service in n/a (medium 5.0)
- [CVE-2001-0513](https://insights.sbomify.com/CVE-2001-0513/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0571 is a high-severity missing authorization vulnerability in Oracle Oracle9i, published on 2 Apr 2003. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-0571 in the wild and no public exploit code.

Affected product: Oracle Oracle9i. 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-0571/ (Markdown: https://insights.sbomify.com/CVE-2002-0571/index.md)
```

## Sources

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

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