# CVE-2017-3528: Open redirect in Applications Framework

> Unauthenticated attackers can exploit open redirects in Oracle E-Business Suite popup windows to modify accessible data via HTTP.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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:** 24 Apr 2017
- **Updated:** 7 Oct 2024
- **Also known as:** GHSA-hcw2-v6gc-xmm9

## What is CVE-2017-3528?

CVE-2017-3528 is a medium-severity vulnerability in Oracle Corporation Applications Framework, published on 24 Apr 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 Applications Framework component of Oracle E-Business Suite (subcomponent: Popup windows (lists of values, datepicker, etc.)). Supported versions that are affected are 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 Applications Framework. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Applications Framework, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Applications Framework accessible data. CVSS 3.0 Base Score 4.7 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N).

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: Oracle Applications Framework.

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

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

## Is CVE-2017-3528 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-3528 exists.

Public exploit code:

- Oracle E-Business Suite 12.1.3/12.2.x - Open Redirect (exploitdb)
- Oracle E-Business Suite 12.1.3/12.2.x - Open Redirect (nuclei): http/cves/2017/CVE-2017-3528.yaml

## Other vulnerabilities in Oracle Corporation Applications Framework

- [CVE-2026-62546](https://insights.sbomify.com/CVE-2026-62546/): Auth bypass in Oracle Applications Framework (critical 9.1)
- [CVE-2021-2200](https://insights.sbomify.com/CVE-2021-2200/): Missing authorization in Applications Framework (critical 9.1)
- [CVE-2026-60675](https://insights.sbomify.com/CVE-2026-60675/): Auth bypass in Oracle Applications Framework (high 8.8)
- [CVE-2026-60676](https://insights.sbomify.com/CVE-2026-60676/): Auth bypass in Oracle Applications Framework (high 8.8)
- [CVE-2026-62534](https://insights.sbomify.com/CVE-2026-62534/): Auth bypass in Oracle Applications Framework (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3528 is a medium-severity vulnerability in Oracle Corporation Applications Framework, published on 24 Apr 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-3528 exists.

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

## Sources

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

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