# CVE-2023-22047: Missing authorization in PeopleSoft Enterprise PT PeopleTools

> Unauthenticated attackers can access critical data in PeopleSoft Enterprise PeopleTools due to missing authorization checks.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2023
- **Updated:** 13 Sep 2024
- **Also known as:** GHSA-5q43-wwhh-v8wh

## What is CVE-2023-22047?

CVE-2023-22047 is a high-severity missing authorization vulnerability in Oracle Peoplesoft Enterprise, published on 18 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the PeopleSoft Enterprise PeopleTools product of Oracle PeopleSoft (component: Portal).  Supported versions that are affected are 8.59 and  8.60. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools.  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all PeopleSoft Enterprise PeopleTools accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2023-22047?

It affects 1 product.


Products: Oracle Peoplesoft Enterprise.

## How do I fix CVE-2023-22047?

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

## Is CVE-2023-22047 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22047 exists.

Public exploit code:

- Leveraging arbitrary file read to RCE on Oracle PeopleSoft (github_poc): https://github.com/tuo4n8/CVE-2023-22047
- CVE-2023-22047 is a critical unauthenticated Local File Inclusion (LFI) vulnerability in Oracle PeopleSoft Enterprise PeopleTools. This exploit allows an attacker to read arbitrary files from the target server without any authentication. (github_poc): https://github.com/0xTerror/CVE-2023-22047---Oracle-PeopleSoft-LFI
- CVE-2023-22047 is a critical unauthenticated Local File Inclusion (LFI) vulnerability in Oracle PeopleSoft Enterprise PeopleTools. This exploit allows an attacker to read arbitrary files from the target server without any authentication. (github_poc): https://github.com/0xTerror/CVE-2023-22047-Oracle-PeopleSoft-LFI
- Oracle Peoplesoft - Unauthenticated File Read (nuclei): http/cves/2023/CVE-2023-22047.yaml

## Other vulnerabilities in Oracle Peoplesoft Enterprise

- [CVE-2007-2131](https://insights.sbomify.com/CVE-2007-2131/): Other in n/a (critical 10.0)
- [CVE-2007-2132](https://insights.sbomify.com/CVE-2007-2132/): Other in n/a (critical 10.0)
- [CVE-2007-2133](https://insights.sbomify.com/CVE-2007-2133/): Other in n/a (critical 10.0)
- [CVE-2006-5375](https://insights.sbomify.com/CVE-2006-5375/): Other in n/a (critical 10.0)
- [CVE-2006-3722](https://insights.sbomify.com/CVE-2006-3722/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22047 and fix it if it is affected.

What it is: CVE-2023-22047 is a high-severity missing authorization vulnerability in Oracle Peoplesoft Enterprise, published on 18 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22047 exists.

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

## Sources

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

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