# CVE-2006-4901: Missing authorization in n/a

> Remote attackers can spoof alerts and conduct replay attacks by invoking eTSAPISend.exe with arbitrary arguments due to missing authorization checks.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/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:** 22 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x2p9-9v87-p988

## What is CVE-2006-4901?

CVE-2006-4901 is a medium-severity missing authorization vulnerability in n/a, published on 22 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Computer Associates (CA) eTrust Security Command Center 1.0 and r8 up to SP1 CR2, and eTrust Audit 1.5 and r8, allows remote attackers to spoof alerts and conduct replay attacks by invoking eTSAPISend.exe with the desired arguments.

## Which versions are affected by CVE-2006-4901?

It affects 4 products.


Products: Broadcom Etrust Audit Client, Broadcom Etrust Audit Datatools, Broadcom Etrust Audit Policy Manager, Broadcom Etrust Security Command Center.

## How do I fix CVE-2006-4901?

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

## Is CVE-2006-4901 being exploited?

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

Public exploit code:

- CA eSCC r8/1.0 / eTrust Audit r8/1.5 - Audit Event System Replay Attack (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4901 and fix it if it is affected.

What it is: CVE-2006-4901 is a medium-severity missing authorization vulnerability in n/a, published on 22 Sep 2006. 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-2006-4901 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-2006-4901/ (Markdown: https://insights.sbomify.com/CVE-2006-4901/index.md)
```

## Sources

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

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