# CVE-2017-3549: SQL injection in Scripting

> Unauthenticated attackers can exploit SQL injection in Oracle Scripting to read, create, delete, or modify critical data via HTTP.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-8jj8-f575-hppp

## What is CVE-2017-3549?

CVE-2017-3549 is a critical SQL injection vulnerability in Oracle Corporation Scripting, published on 24 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Scripting component of Oracle E-Business Suite (subcomponent: Scripting Administration). 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 Scripting. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Scripting accessible data as well as unauthorized access to critical data or complete access to all Oracle Scripting accessible data. CVSS 3.0 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Oracle Scripting.

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

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

## Is CVE-2017-3549 being exploited?

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

Public exploit code:

- Oracle E-Business Suite 12.2.3 - 'IESFOOTPRINT' SQL Injection (exploitdb)

## Other vulnerabilities in Oracle Corporation Scripting

- [CVE-2021-2029](https://insights.sbomify.com/CVE-2021-2029/): Auth bypass in Scripting (critical 9.8)
- [CVE-2026-60976](https://insights.sbomify.com/CVE-2026-60976/): Auth bypass in Oracle Scripting (high 8.8)
- [CVE-2021-2091](https://insights.sbomify.com/CVE-2021-2091/): Cross-site scripting in Scripting (high 8.2)
- [CVE-2020-2817](https://insights.sbomify.com/CVE-2020-2817/): Cross-site scripting in Scripting (high 8.2)
- [CVE-2020-2879](https://insights.sbomify.com/CVE-2020-2879/): Cross-site scripting in Scripting (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3549 is a critical SQL injection vulnerability in Oracle Corporation Scripting, published on 24 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3549 in the wild and no public exploit code.

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

## Sources

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

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