# CVE-2011-0854: Other in n/a

> Remote authenticated users can compromise confidentiality and integrity in Oracle PeopleSoft HRMS via unspecified ePerformance vectors.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:P/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:** 20 Apr 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-c2f8-j24w-jffj

## What is CVE-2011-0854?

CVE-2011-0854 is a medium-severity vulnerability in n/a, published on 20 Apr 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in Oracle PeopleSoft Enterprise HRMS 9.1 Bundle #5 allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to ePerformance.

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

It affects 1 product.


Products: Oracle Peoplesoft Enterprise Hrms.

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

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

## Is CVE-2011-0854 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-3527](https://insights.sbomify.com/CVE-2011-3527/): Other in n/a (medium 5.5)
- [CVE-2011-3533](https://insights.sbomify.com/CVE-2011-3533/): Missing authorization in n/a (medium 5.5)
- [CVE-2011-2279](https://insights.sbomify.com/CVE-2011-2279/): Other in n/a (medium 5.5)
- [CVE-2011-0853](https://insights.sbomify.com/CVE-2011-0853/): Other in n/a (medium 5.5)
- [CVE-2011-0857](https://insights.sbomify.com/CVE-2011-0857/): Other in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-0854 is a medium-severity vulnerability in n/a, published on 20 Apr 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-0854 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-0854/ (Markdown: https://insights.sbomify.com/CVE-2011-0854/index.md)
```

## Sources

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

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