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

> Remote attackers can add users or IDS rules without authentication, leading to unauthorized access and configuration changes.

- **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:** 2 Dec 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-x29m-6pxm-hmh5

## What is CVE-2003-0974?

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

### Official description

Applied Watch Command Center allows remote attackers to conduct unauthorized activities without authentication, such as (1) add new users to a console, as demonstrated using appliedsnatch.c, or (2) add spurious IDS rules to sensors, as demonstrated using addrule.c.

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

It affects 1 product.


Products: Applied Watch Technologies Applied Watch Command Center.

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

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

## Is CVE-2003-0974 being exploited?

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

Public exploit code:

- Applied Watch Command Center 1.0 - Authentication Bypass (1) (exploitdb)
- Applied Watch Command Center 1.0 - Authentication Bypass (2) (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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