# CVE-2017-10304: Cross-site request forgery in PeopleSoft Enterprise HCM Human Resources

> Low-privileged attackers can exploit CSRF in PeopleSoft HCM to modify or read data, requiring victim interaction.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Oct 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-8q8h-mrhg-f3gq

## What is CVE-2017-10304?

CVE-2017-10304 is a medium-severity vulnerability in Oracle Corporation PeopleSoft Enterprise HCM Human Resources, published on 19 Oct 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the PeopleSoft Enterprise HCM component of Oracle PeopleSoft Products (subcomponent: Security). The supported version that is affected is 9.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise HCM. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in PeopleSoft Enterprise HCM, 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 HCM accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise HCM accessible data. CVSS 3.0 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).

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

It affects 1 product.


Products: Oracle Peoplesoft Enterprise Human Capital Management Human Resources.

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

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

## Is CVE-2017-10304 being exploited?

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

## Other vulnerabilities in Oracle Corporation PeopleSoft Enterprise HCM Human Resources

- [CVE-2016-0407](https://insights.sbomify.com/CVE-2016-0407/): Information disclosure in n/a (medium 6.5)
- [CVE-2018-3068](https://insights.sbomify.com/CVE-2018-3068/): Cross-site scripting in PeopleSoft Enterprise HCM Human Resources (medium 6.1)
- [CVE-2018-2654](https://insights.sbomify.com/CVE-2018-2654/): Cross-site scripting in PeopleSoft Enterprise HCM Human Resources (medium 6.1)
- [CVE-2023-21992](https://insights.sbomify.com/CVE-2023-21992/): Missing authorization in PeopleSoft Enterprise HCM Human Resources (medium 5.4)
- [CVE-2018-2681](https://insights.sbomify.com/CVE-2018-2681/): Missing authorization in PeopleSoft Enterprise HCM Human Resources (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10304 is a medium-severity vulnerability in Oracle Corporation PeopleSoft Enterprise HCM Human Resources, published on 19 Oct 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-10304 in the wild and no public exploit code.

Affected product: Oracle Corporation PeopleSoft Enterprise HCM Human Resources. 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-10304/ (Markdown: https://insights.sbomify.com/CVE-2017-10304/index.md)
```

## Sources

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

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