# CVE-2005-2187: Missing authorization in n/a

> Authenticated users can bypass access controls to modify alerts and generate reports by manipulating specific parameters.

- **Severity:** Medium 4.6 (`AV:L/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:** 10 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xh44-8w9g-3p27

## What is CVE-2005-2187?

CVE-2005-2187 is a medium-severity missing authorization vulnerability in n/a, published on 10 Jul 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

McAfee IntruShield Security Management System allows remote authenticated users to access the "Generate Reports" feature and modify alerts by setting the Access option to true, as demonstrated using the (1) fullAccess or (2) fullAccessRight parameter in reports-column-center.jsp, or (3) fullAccess parameter to SystemEvent.jsp.

## Which versions are affected by CVE-2005-2187?

It affects 1 product.


Products: Mcafee Intrushield Security Management System.

## How do I fix CVE-2005-2187?

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

## Is CVE-2005-2187 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2188](https://insights.sbomify.com/CVE-2005-2188/): Auth bypass in n/a (high 7.5)
- [CVE-2005-2186](https://insights.sbomify.com/CVE-2005-2186/): Cross-site scripting in n/a (low 1.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2187 and fix it if it is affected.

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

## Sources

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

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