# CVE-2008-1815: SQL injection in n/a

> Authenticated attackers can exploit SQL injection in Oracle Database Change Data Capture to read or modify data.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:N`)
- **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:** 16 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5jcx-hp3j-qqqm

## What is CVE-2008-1815?

CVE-2008-1815 is a medium-severity SQL injection vulnerability in n/a, published on 16 Apr 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the Change Data Capture component in Oracle Database 10.1.0.5, 10.2.0.3, and 11.1.0.6 has unknown impact and remote authenticated attack vectors related to DBMS_CDC_UTILITY, aka DB02.  NOTE: the previous information was obtained from the April 2008 CPU.  Oracle has not commented on reliable researcher claims that DB02 is for SQL injection in LOCK_CHANGE_SET.

## Which versions are affected by CVE-2008-1815?

It affects 2 products.


Products: Oracle Database 10g, Oracle Database 11g.

## How do I fix CVE-2008-1815?

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

## Is CVE-2008-1815 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0985](https://insights.sbomify.com/CVE-2009-0985/): Other in n/a (high 7.1)
- [CVE-2008-2624](https://insights.sbomify.com/CVE-2008-2624/): Other in n/a (medium 6.5)
- [CVE-2008-3989](https://insights.sbomify.com/CVE-2008-3989/): Other in n/a (medium 6.5)
- [CVE-2009-0975](https://insights.sbomify.com/CVE-2009-0975/): Information disclosure in n/a (medium 5.5)
- [CVE-2009-0976](https://insights.sbomify.com/CVE-2009-0976/): Missing authorization in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1815 and fix it if it is affected.

What it is: CVE-2008-1815 is a medium-severity SQL injection vulnerability in n/a, published on 16 Apr 2008. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-1815 in the wild and no public exploit code.

Affected product: n/a. 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-2008-1815/ (Markdown: https://insights.sbomify.com/CVE-2008-1815/index.md)
```

## Sources

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

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