# CVE-2011-1046: Missing authorization in n/a

> Remote attackers with low privileges can modify privileged object properties in IBM FileNet P8 Content Engine due to missing authorization checks.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **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:** 21 Feb 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v725-vrpf-8mgm

## What is CVE-2011-1046?

CVE-2011-1046 is a medium-severity missing authorization vulnerability in n/a, published on 21 Feb 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM FileNet P8 Content Engine (aka P8CE) 4.0.1 through 5.0.0, as used in FileNet P8 Content Manager (CM) and FileNet P8 Business Process Manager (BPM), does not require the PRIVILEGED_WRITE access role for all intended Object Store modifications, which allows remote attackers to change a privileged property of an object via unspecified vectors.

Weakness: CWE-264

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

It affects 3 products.


Products: Ibm Filenet P8 Business Process Manager, Ibm Filenet P8 Content Engine, Ibm Filenet P8 Content Manager.

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

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

## Is CVE-2011-1046 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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