CVE-2017-3549 SQL injection in Scripting

Critical 9.1 Published 24 Apr 2017 Updated 4 Oct 2024

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

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

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

Which versions are affected by CVE-2017-3549?

It affects 1 product.

Products include 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.

Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.

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: 1 Exploit-DB entry.

Sources

Also known as GHSA-8jj8-f575-hppp.