# CVE-2007-5511: SQL injection in n/a

> Attackers can execute arbitrary SQL commands via the FINDRICSET procedure in Oracle Workspace Manager, potentially compromising database 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:** 17 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mv98-3pjv-4gv2

## What is CVE-2007-5511?

CVE-2007-5511 is a medium-severity SQL injection vulnerability in Oracle Database Server, published on 17 Oct 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in Workspace Manager for Oracle Database before OWM 10.2.0.4.1, OWM 10.1.0.8.0, and OWM 9.2.0.8.0 allows attackers to execute arbitrary SQL commands via the FINDRICSET procedure in the LT package.  NOTE: this is probably covered by CVE-2007-5510, but there are insufficient details to be certain.

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

## Which versions are affected by CVE-2007-5511?

It affects 1 product.


Products: Oracle Database Server.

## How do I fix CVE-2007-5511?

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

## Is CVE-2007-5511 being exploited?

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

Public exploit code:

- Oracle DB SQL Injection via SYS.LT.FINDRICSET Evil Cursor Method (metasploit)
- Oracle 10g/11g - 'SYS.LT.FINDRICSET' SQL Injection (1) (exploitdb)
- Oracle 10g/11g - 'SYS.LT.FINDRICSET' SQL Injection (2) (exploitdb)
- Oracle 10g - 'LT.FINDRICSET' SQL Injection (IDS Evasion) (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-2007-5511 and fix it if it is affected.

What it is: CVE-2007-5511 is a medium-severity SQL injection vulnerability in Oracle Database Server, published on 17 Oct 2007. Any signed-in user can exploit it 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-2007-5511 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-2007-5511/ (Markdown: https://insights.sbomify.com/CVE-2007-5511/index.md)
```

## Sources

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

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