# CVE-2017-3577: Missing authorization in PeopleSoft Enterprise CS Campus Community

> High-privileged attackers can bypass authorization to read, create, delete, or modify critical data in PeopleSoft Campus Community.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-6mvx-gh55-4f4p

## What is CVE-2017-3577?

CVE-2017-3577 is a medium-severity missing authorization vulnerability in Oracle Corporation PeopleSoft Enterprise CS Campus Community, published on 24 Apr 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in the PeopleSoft Enterprise CS Campus Community component of Oracle PeopleSoft Products (subcomponent: Frameworks). The supported version that is affected is 9.2. Easily "exploitable" vulnerability allows high privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise CS Campus Community. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all PeopleSoft Enterprise CS Campus Community accessible data as well as unauthorized access to critical data or complete access to all PeopleSoft Enterprise CS Campus Community accessible data. CVSS 3.0 Base Score 6.5 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N).

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

It affects 1 product.


Products: Oracle Peoplesoft Enterprise Campus Software Campus Community.

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

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

## Is CVE-2017-3577 being exploited?

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

## Other vulnerabilities in Oracle Corporation PeopleSoft Enterprise CS Campus Community

- [CVE-2026-60594](https://insights.sbomify.com/CVE-2026-60594/): Auth bypass in PeopleSoft Enterprise CS Campus Community (high 8.8)
- [CVE-2026-60603](https://insights.sbomify.com/CVE-2026-60603/): Auth bypass in PeopleSoft Enterprise CS Student Records (high 8.8)
- [CVE-2026-60615](https://insights.sbomify.com/CVE-2026-60615/): Auth bypass in PeopleSoft Enterprise CS Campus Community (high 8.2)
- [CVE-2026-60599](https://insights.sbomify.com/CVE-2026-60599/): Missing authorization in PeopleSoft Enterprise CS Student Records (high 8.1)
- [CVE-2026-46851](https://insights.sbomify.com/CVE-2026-46851/): Code injection in PeopleSoft Enterprise CS Campus Community (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3577 is a medium-severity missing authorization vulnerability in Oracle Corporation PeopleSoft Enterprise CS Campus Community, published on 24 Apr 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3577 in the wild and no public exploit code.

Affected product: Oracle Corporation PeopleSoft Enterprise CS Campus Community. 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-3577/ (Markdown: https://insights.sbomify.com/CVE-2017-3577/index.md)
```

## Sources

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

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