# CVE-2004-1339: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via vulnerable database triggers, potentially compromising data integrity and confidentiality.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-7v5p-vcr4-vrxf

## What is CVE-2004-1339?

CVE-2004-1339 is a medium-severity SQL injection vulnerability in Oracle Database Server, published on 6 Jan 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in the (1) MDSYS.SDO_GEOM_TRIG_INS1 and (2) MDSYS.SDO_LRS_TRIG_INS default triggers in Oracle 9i and 10g allows remote attackers to execute arbitrary SQL commands via the new.table_name or new.column_name parameters.

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

## Which versions are affected by CVE-2004-1339?

It affects 2 products.


Products: Oracle Database Server, Oracle Oracle9i.

## How do I fix CVE-2004-1339?

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

## Is CVE-2004-1339 being exploited?

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

## 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-2004-1339 and fix it if it is affected.

What it is: CVE-2004-1339 is a medium-severity SQL injection vulnerability in Oracle Database Server, published on 6 Jan 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-1339 in the wild and no public exploit code.

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-2004-1339/ (Markdown: https://insights.sbomify.com/CVE-2004-1339/index.md)
```

## Sources

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

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