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

> Attackers can bypass document access controls via direct API calls to read restricted data in Lotus Domino servers.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-w4q4-x7m7-mhhx

## What is CVE-2002-0037?

CVE-2002-0037 is a high-severity missing authorization vulnerability in n/a, published on 12 Apr 2002. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Lotus Domino Servers 5.x, 4.6x, and 4.5x allows attackers to bypass the intended Reader and Author access list for a document's object via a Notes API call (NSFDbReadObject) that directly accesses the object.

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

It affects 1 product.


Products: Ibm Lotus Domino Server.

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

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

## Is CVE-2002-0037 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1101](https://insights.sbomify.com/CVE-2005-1101/): Memory corruption in n/a (high 7.5)
- [CVE-2006-0580](https://insights.sbomify.com/CVE-2006-0580/): Denial of service in n/a (medium 5.0)
- [CVE-2002-2025](https://insights.sbomify.com/CVE-2002-2025/): Denial of service in n/a (medium 5.0)
- [CVE-2005-0986](https://insights.sbomify.com/CVE-2005-0986/): Denial of service in n/a (medium 5.0)
- [CVE-1999-0729](https://insights.sbomify.com/CVE-1999-0729/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0037 is a high-severity missing authorization vulnerability in n/a, published on 12 Apr 2002. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-0037 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-0037/ (Markdown: https://insights.sbomify.com/CVE-2002-0037/index.md)
```

## Sources

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

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