# CVE-2006-0549: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands in Oracle Database via the SYS.DBMS_METADATA_UTIL package, potentially compromising data integrity and confidentiality.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-ff55-4qfm-2hmv

## What is CVE-2006-0549?

CVE-2006-0549 is a high-severity SQL injection vulnerability in Oracle Database Server, published on 4 Feb 2006. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in the SYS.DBMS_METADATA_UTIL package in Oracle Database 10g, and possibly earlier versions, might allow remote attackers to execute arbitrary SQL commands via unknown vectors. NOTE: due to the lack of relevant details from the Oracle advisory, a separate CVE is being created since it cannot be conclusively proven that this issue has been addressed by Oracle.  It is possible that this is the same issue as Oracle Vuln# DB05 from the January 2006 CPU, in which case this would be subsumed by CVE-2006-0260.  However, there are some inconsistencies that make this unclear, and there is also a possibility that this is related to DB06, which is subsumed by CVE-2006-0259.

## Which versions are affected by CVE-2006-0549?

It affects 1 product.


Products: Oracle Database Server.

## How do I fix CVE-2006-0549?

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

## Is CVE-2006-0549 being exploited?

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

Public exploit code:

- Oracle 9i/10g - DBMS_METADATA.GET_DDL SQL Injection (exploitdb)
- Oracle 9i/10g DBMS_METADATA.GET_DDL - SQL Injection (2) (exploitdb)

## Other vulnerabilities in Oracle Database Server

- [CVE-2015-4863](https://insights.sbomify.com/CVE-2015-4863/): Other in n/a (critical 10.0)
- [CVE-2013-1534](https://insights.sbomify.com/CVE-2013-1534/): Other in n/a (critical 10.0)
- [CVE-2010-0071](https://insights.sbomify.com/CVE-2010-0071/): Other in n/a (critical 10.0)
- [CVE-2009-1979](https://insights.sbomify.com/CVE-2009-1979/): Other in n/a (critical 10.0)
- [CVE-2009-1985](https://insights.sbomify.com/CVE-2009-1985/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0549 and fix it if it is affected.

What it is: CVE-2006-0549 is a high-severity SQL injection vulnerability in Oracle Database Server, published on 4 Feb 2006. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0549 exists.

Affected product: Oracle Database Server. 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-2006-0549/ (Markdown: https://insights.sbomify.com/CVE-2006-0549/index.md)
```

## Sources

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

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