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

> Remote authenticated users can compromise confidentiality and integrity in PeopleSoft FSCM eProcurement via unspecified 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:** 21 Jul 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2749-8q36-jm57

## What is CVE-2011-2272?

CVE-2011-2272 is a medium-severity vulnerability in Oracle Peoplesoft Products, published on 21 Jul 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the PeopleSoft Enterprise FSCM component in Oracle PeopleSoft Products 9.0, Bundle, #36, 9.1, Bundle, and #13 allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to eProcurement.

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

It affects 2 products.


Products: Oracle Peoplesoft Enterprise Fscm, Oracle Peoplesoft Products.

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

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

## Is CVE-2011-2272 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2272 is a medium-severity vulnerability in Oracle Peoplesoft Products, published on 21 Jul 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-2272 in the wild and no public exploit code.

Affected product: Oracle Peoplesoft Products. 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-2272/ (Markdown: https://insights.sbomify.com/CVE-2011-2272/index.md)
```

## Sources

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

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