# CVE-2006-4991: Security feature bypass in n/a

> Privileged local users can bypass audit integrity checks in RSA KeonCA Manager to hide malicious Certificate Authority activities.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r9v4-2qh5-jc2c

## What is CVE-2006-4991?

CVE-2006-4991 is a low-severity vulnerability in n/a, published on 26 Sep 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

RSA Keon Certificate Authority (KeonCA) Manager 6.5.1 and 6.6 allows privileged local users to hide malicious Certificate Authority (CA) activities by modifying CA auditor logs without detection by (1) modifying or deleting a <LOG BLOCK> and its signature from the XML log in a way that is not detected by the integrity check function that operates on the entire pool, or (2) modifying entries in the live log file, which is only signed during rotation.

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

It affects 1 product.


Products: Rsa Keon Certificate Authority Manager.

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

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

## Is CVE-2006-4991 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4991 is a low-severity vulnerability in n/a, published on 26 Sep 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4991 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-2006-4991/ (Markdown: https://insights.sbomify.com/CVE-2006-4991/index.md)
```

## Sources

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

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