# CVE-2017-3263: Missing authorization in Primavera P6 Enterprise Project Portfolio Management

> Low-privileged attackers can modify or access critical project data in Oracle Primavera P6 via HTTP without proper authorization checks.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 27 Jan 2017
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-5jxf-jfh8-9h7w

## What is CVE-2017-3263?

CVE-2017-3263 is a high-severity missing authorization vulnerability in Oracle Primavera P6 Enterprise Project Portfolio Management, published on 27 Jan 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Primavera P6 Enterprise Project Portfolio Management component of Oracle Primavera Products Suite (subcomponent: Team Member). Supported versions that are affected are 8.2, 8.3, 8.4, 15.1, 15.2, 16.1 and 16.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Primavera P6 Enterprise Project Portfolio Management. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Primavera P6 Enterprise Project Portfolio Management accessible data as well as unauthorized access to critical data or complete access to all Primavera P6 Enterprise Project Portfolio Management accessible data. CVSS v3.0 Base Score 8.1 (Confidentiality and Integrity impacts).

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

It affects 1 product.


Products: Oracle Primavera P6 Enterprise Project Portfolio Management.

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

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

## Is CVE-2017-3263 being exploited?

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

## Other vulnerabilities in Oracle Primavera P6 Enterprise Project Portfolio Management

- [CVE-2017-3324](https://insights.sbomify.com/CVE-2017-3324/): Missing authorization in Primavera P6 Enterprise Project Portfolio Management (critical 10.0)
- [CVE-2017-3503](https://insights.sbomify.com/CVE-2017-3503/): Deserialization in Primavera P6 Enterprise Project Portfolio Management (critical 9.9)
- [CVE-2019-3020](https://insights.sbomify.com/CVE-2019-3020/): Cross-site scripting in Primavera P6 Enterprise Project Portfolio Management (critical 9.3)
- [CVE-2024-21095](https://insights.sbomify.com/CVE-2024-21095/): Information disclosure in Primavera P6 Enterprise Project Portfolio Management (high 8.2)
- [CVE-2017-3583](https://insights.sbomify.com/CVE-2017-3583/): Cross-site request forgery in Primavera P6 Enterprise Project Portfolio Management (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3263 is a high-severity missing authorization vulnerability in Oracle Primavera P6 Enterprise Project Portfolio Management, published on 27 Jan 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3263 in the wild and no public exploit code.

Affected product: Oracle Primavera P6 Enterprise Project Portfolio Management. 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-3263/ (Markdown: https://insights.sbomify.com/CVE-2017-3263/index.md)
```

## Sources

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

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