# CVE-2011-1045: Privilege escalation in n/a

> Remote attackers can gain privileges in IBM FileNet P8 Content Manager via unspecified vectors in the Rendition Engine.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 21 Feb 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gfff-p3q7-9jjv

## What is CVE-2011-1045?

CVE-2011-1045 is a medium-severity vulnerability in n/a, published on 21 Feb 2011. It can be exploited over the network.

### Official description

Unspecified vulnerability in the Rendition Engine (aka P8RE) 4.0.1 through 4.5.1 in IBM FileNet P8 Content Manager (CM) allows remote attackers to gain privileges via unknown vectors.

## Which versions are affected by CVE-2011-1045?

It affects 2 products.


Products: Ibm Filenet P8 Content Manager, Ibm Filenet P8 Rendition Engine.

## How do I fix CVE-2011-1045?

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

## Is CVE-2011-1045 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1045 and fix it if it is affected.

What it is: CVE-2011-1045 is a medium-severity vulnerability in n/a, published on 21 Feb 2011. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2011-1045 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-2011-1045/ (Markdown: https://insights.sbomify.com/CVE-2011-1045/index.md)
```

## Sources

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

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