# CVE-2017-10061: Missing authorization in PeopleSoft Enterprise PT PeopleTools

> Unauthenticated attackers can compromise PeopleSoft Integration Broker to read, modify, or delete data and cause partial denial of service.

- **Severity:** High 8.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Aug 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-76gc-487q-j62w

## What is CVE-2017-10061?

CVE-2017-10061 is a high-severity missing authorization vulnerability in Oracle Peoplesoft Enterprise Peopletools, published on 8 Aug 2017. 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 component of Oracle PeopleSoft Products (subcomponent: Integration Broker). Supported versions that are affected are 8.54 and 8.55. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. While the vulnerability is in PeopleSoft Enterprise PeopleTools, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of PeopleSoft Enterprise PeopleTools accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise PeopleTools accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of PeopleSoft Enterprise PeopleTools. CVSS 3.0 Base Score 8.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L).

## Which versions are affected by CVE-2017-10061?

It affects 1 product.


Products: Oracle Peoplesoft Enterprise Peopletools.

## How do I fix CVE-2017-10061?

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

## Is CVE-2017-10061 being exploited?

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

## Other vulnerabilities in Oracle Peoplesoft Enterprise Peopletools

- [CVE-2026-35273](https://insights.sbomify.com/CVE-2026-35273/): Oracle PeopleSoft Enterprise PeopleTools Missing Authentication for Critical Function (critical 9.8, exploited in the wild)
- [CVE-2026-60821](https://insights.sbomify.com/CVE-2026-60821/): Auth bypass in PeopleSoft Enterprise PeopleTools (critical 9.8)
- [CVE-2022-21543](https://insights.sbomify.com/CVE-2022-21543/): Auth bypass in PeopleSoft Enterprise PT PeopleTools (critical 9.8)
- [CVE-2017-10366](https://insights.sbomify.com/CVE-2017-10366/): Auth bypass in PeopleSoft Enterprise PT PeopleTools (critical 9.8)
- [CVE-2026-101420](https://insights.sbomify.com/CVE-2026-101420/): Vulnerability in the PeopleSoft Enterprise PeopleTools product of Oracle PeopleSoft (component: SQR). (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10061 and fix it if it is affected.

What it is: CVE-2017-10061 is a high-severity missing authorization vulnerability in Oracle Peoplesoft Enterprise Peopletools, published on 8 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10061 in the wild and no public exploit code.

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

## Sources

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

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