# CVE-2003-0941: Missing authorization in n/a

> Remote attackers can access SAP DB Web Agent Administration pages and modify configuration without authentication via direct requests.

- **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:** 21 Nov 2003
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-69jx-6576-7762

## What is CVE-2003-0941?

CVE-2003-0941 is a high-severity missing authorization vulnerability in n/a, published on 21 Nov 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

web-tools in SAP DB before 7.4.03.30 allows remote attackers to access the Web Agent Administration pages and modify configuration via a direct request to waadmin.wa.

## Which versions are affected by CVE-2003-0941?

It affects 1 product.


Products: Sap Sap Db.

## How do I fix CVE-2003-0941?

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

## Is CVE-2003-0941 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3614](https://insights.sbomify.com/CVE-2007-3614/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0939](https://insights.sbomify.com/CVE-2003-0939/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0942](https://insights.sbomify.com/CVE-2003-0942/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0943](https://insights.sbomify.com/CVE-2003-0943/): Information disclosure in n/a (high 7.5)
- [CVE-2003-0944](https://insights.sbomify.com/CVE-2003-0944/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0941 and fix it if it is affected.

What it is: CVE-2003-0941 is a high-severity missing authorization vulnerability in n/a, published on 21 Nov 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-2003-0941 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-2003-0941/ (Markdown: https://insights.sbomify.com/CVE-2003-0941/index.md)
```

## Sources

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

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