# CVE-2017-3446: Cross-site scripting in Trade Management

> Unauthenticated attackers can exploit a cross-site scripting flaw in Oracle Trade Management to access and modify sensitive data 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:** 19 Oct 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-w9xf-22f4-g98c

## What is CVE-2017-3446?

CVE-2017-3446 is a high-severity cross-site scripting vulnerability in Oracle Corporation Trade Management, published on 19 Oct 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 Trade Management component of Oracle E-Business Suite (subcomponent: User Interface). 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 Trade Management. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Trade Management, 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 Trade Management accessible data as well as unauthorized update, insert or delete access to some of Oracle Trade Management accessible data. CVSS 3.0 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N).

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

It affects 1 product.


Products: Oracle Trade Management.

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

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

## Is CVE-2017-3446 being exploited?

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

## Other vulnerabilities in Oracle Corporation Trade Management

- [CVE-2020-14876](https://insights.sbomify.com/CVE-2020-14876/): Missing authorization in Trade Management (critical 9.1)
- [CVE-2020-14665](https://insights.sbomify.com/CVE-2020-14665/): Missing authorization in Trade Management (critical 9.1)
- [CVE-2026-62447](https://insights.sbomify.com/CVE-2026-62447/): Auth bypass in Oracle Trade Management (high 8.8)
- [CVE-2021-2206](https://insights.sbomify.com/CVE-2021-2206/): Cross-site scripting in Trade Management (high 8.2)
- [CVE-2021-2210](https://insights.sbomify.com/CVE-2021-2210/): Cross-site scripting in Trade Management (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3446 is a high-severity cross-site scripting vulnerability in Oracle Corporation Trade Management, published on 19 Oct 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-3446 in the wild and no public exploit code.

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

## Sources

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

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