# CVE-2017-3328: Cross-site scripting in Common Applications 12.1.1;12.1.2;12.1.3;12.2.3;12.2.4;12.2.5;12.2.6

> Unauthenticated attackers can exploit this vulnerability to access critical data and modify some data in Oracle E-Business Suite via HTTP.

- **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/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:** 27 Jan 2017
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-w6hp-mp6v-hq3f

## What is CVE-2017-3328?

CVE-2017-3328 is a high-severity cross-site scripting vulnerability in Common Applications 12.1.1;12.1.2;12.1.3;12.2.3;12.2.4;12.2.5;12.2.6, published on 27 Jan 2017. 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 Oracle Common Applications component of Oracle E-Business Suite (subcomponent: Resources Module). Supported versions that are affected are 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5 and 12.2.6. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Common Applications. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Common Applications, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Common Applications accessible data as well as unauthorized update, insert or delete access to some of Oracle Common Applications accessible data. CVSS v3.0 Base Score 8.2 (Confidentiality and Integrity impacts).

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

It affects 1 product.


Products: Oracle Common Applications.

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

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

## Is CVE-2017-3328 being exploited?

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

## Other vulnerabilities in Common Applications 12.1.1;12.1.2;12.1.3;12.2.3;12.2.4;12.2.5;12.2.6

- [CVE-2017-10330](https://insights.sbomify.com/CVE-2017-10330/): Missing authorization in Common Applications (critical 9.1)
- [CVE-2021-2436](https://insights.sbomify.com/CVE-2021-2436/): Cross-site scripting in Common Applications (high 8.2)
- [CVE-2021-2093](https://insights.sbomify.com/CVE-2021-2093/): Cross-site scripting in Common Applications (high 8.2)
- [CVE-2020-14688](https://insights.sbomify.com/CVE-2020-14688/): Cross-site scripting in Common Applications (high 8.2)
- [CVE-2019-2665](https://insights.sbomify.com/CVE-2019-2665/): Cross-site scripting in Common Applications (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3328 is a high-severity cross-site scripting vulnerability in Common Applications 12.1.1;12.1.2;12.1.3;12.2.3;12.2.4;12.2.5;12.2.6, published on 27 Jan 2017. 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-2017-3328 in the wild and no public exploit code.

Affected product: Common Applications 12.1.1;12.1.2;12.1.3;12.2.3;12.2.4;12.2.5;12.2.6. 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-3328/ (Markdown: https://insights.sbomify.com/CVE-2017-3328/index.md)
```

## Sources

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

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