# CVE-2020-14549: Information disclosure in Primavera Portfolio Management

> Unauthenticated attackers can access critical data and modify some records in Oracle Primavera Portfolio Management via HTTPS, requiring user interaction.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jul 2020
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-cc7x-rwq6-84vw

## What is CVE-2020-14549?

CVE-2020-14549 is a medium-severity vulnerability in Oracle Corporation Primavera Portfolio Management, published on 15 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Primavera Portfolio Management product of Oracle Construction and Engineering (component: Web Server). Supported versions that are affected are 16.1.0.0-16.1.5.1, 18.0.0.0-18.0.2.0 and 19.0.0.0. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTPS to compromise Primavera Portfolio Management. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Primavera Portfolio Management accessible data as well as unauthorized update, insert or delete access to some of Primavera Portfolio Management accessible data. CVSS 3.1 Base Score 5.9 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N).

## Which versions are affected by CVE-2020-14549?

It affects 1 product.


Products: Oracle Primavera Portfolio Management.

## How do I fix CVE-2020-14549?

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

## Is CVE-2020-14549 being exploited?

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

## Other vulnerabilities in Oracle Corporation Primavera Portfolio Management

- [CVE-2022-21269](https://insights.sbomify.com/CVE-2022-21269/): Cross-site scripting in Primavera Portfolio Management (medium 6.1)
- [CVE-2020-14528](https://insights.sbomify.com/CVE-2020-14528/): Cross-site scripting in Primavera Portfolio Management (medium 6.1)
- [CVE-2020-2562](https://insights.sbomify.com/CVE-2020-2562/): Cross-site scripting in Primavera Portfolio Management (medium 6.1)
- [CVE-2020-14527](https://insights.sbomify.com/CVE-2020-14527/): Information disclosure in Primavera Portfolio Management (medium 5.9)
- [CVE-2022-21242](https://insights.sbomify.com/CVE-2022-21242/): Cross-site scripting in Primavera Portfolio Management (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14549 and fix it if it is affected.

What it is: CVE-2020-14549 is a medium-severity vulnerability in Oracle Corporation Primavera Portfolio Management, published on 15 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-14549 in the wild and no public exploit code.

Affected product: Oracle Corporation Primavera 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-2020-14549/ (Markdown: https://insights.sbomify.com/CVE-2020-14549/index.md)
```

## Sources

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

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