# CVE-2008-2607: Memory corruption in n/a

> Authenticated attackers can trigger a buffer overflow in Oracle Database Advanced Queuing, potentially causing denial of service or arbitrary code execution.

- **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:** 15 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hjq3-j9hq-m46w

## What is CVE-2008-2607?

CVE-2008-2607 is a medium-severity memory corruption vulnerability in Oracle Database Server, published on 15 Jul 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the Advanced Queuing component in Oracle Database 9.2.0.8, 9.2.0.8DV, 10.1.0.5, 10.2.0.4, and 11.1.0.6 has unknown impact and remote authenticated attack vectors related to SYS.DBMS_AQELM.  NOTE: the previous information was obtained from the Oracle July 2008 CPU.  Oracle has not commented on reliable researcher claims that this issue is a buffer overflow that allows attackers to cause a denial of service (database corruption) and possibly execute arbitrary code via a long argument to an unspecified procedure.

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

It affects 3 products.


Products: Oracle Advanced Queuing Component, Oracle Database 9i, Oracle Database Server.

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

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

## Is CVE-2008-2607 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2607 is a medium-severity memory corruption vulnerability in Oracle Database Server, published on 15 Jul 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-2607 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-2008-2607/ (Markdown: https://insights.sbomify.com/CVE-2008-2607/index.md)
```

## Sources

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

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