CVE-2006-0271 SQL injection in n/a

Critical 10.0 Published 18 Jan 2006 Updated 7 Aug 2024

SQL injection in Oracle Database DBMS_REGISTRY package allows attackers to execute arbitrary code or read data.

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

What is CVE-2006-0271?

CVE-2006-0271 is a critical SQL injection vulnerability in Oracle Database Server, published on 18 Jan 2006. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Unspecified vulnerability in the Upgrade & Downgrade component of Oracle Database server 8.1.7.4, 9.0.1.5, 9.2.0.7, and 10.1.0.4 has unspecified impact and attack vectors, as identified by Oracle Vuln# DB28. NOTE: details are unavailable from Oracle, but they have not publicly disputed a claim by a reliable independent researcher that states that the problem is SQL injection in the DBMS_REGISTRY package in certain parameters to the (1) IS_COMPONENT, (2) GET_COMP_OPTION, (3) DISABLE_DDL_TRIGGERS, (4) SCRIPT_EXISTS, (5) COMP_PATH, (6) GATHER_STATS, (7) NOTHING_SCRIPT, and (8) VALIDATE_COMPONENTS functions.

Which versions are affected by CVE-2006-0271?

It affects 4 products.

Products include Oracle Database Server, Oracle Oracle10g, Oracle Oracle8i, Oracle Oracle9i.

How do I fix CVE-2006-0271?

No fix has been published for CVE-2006-0271 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-2006-0271 being exploited?

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

All Oracle Database Server vulnerabilities

Sources

Also known as GHSA-phg8-vw44-8h8q.