# CVE-2007-5090: Other in n/a

> Attackers can corrupt data in IBM Rational ClearQuest when using Microsoft SQL Server or IBM DB2 databases.

- **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:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 26 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hjgh-mjrj-x6h8

## What is CVE-2007-5090?

CVE-2007-5090 is a high-severity vulnerability in n/a, published on 26 Sep 2007. 

### Official description

Unspecified vulnerability in IBM Rational ClearQuest (CQ), when a Microsoft SQL Server or an IBM DB2 database is used, allows attackers to corrupt data via unspecified vectors.

Weakness: CWE-264

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

It affects 1 product.


Products: Ibm Rational Clearquest.

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

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

## Is CVE-2007-5090 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4601](https://insights.sbomify.com/CVE-2010-4601/): Other in n/a (critical 10.0)
- [CVE-2012-0708](https://insights.sbomify.com/CVE-2012-0708/): Memory corruption in n/a (critical 9.3)
- [CVE-2011-1390](https://insights.sbomify.com/CVE-2011-1390/): SQL injection in n/a (high 7.5)
- [CVE-2010-2517](https://insights.sbomify.com/CVE-2010-2517/): Multiple unspecified vulnerabilities in IBM Rational ClearQuest before 7.1.1.02 have unknown impact and attack vectors, as demonstrated by an AppScan report. (high 7.5)
- [CVE-2008-5329](https://insights.sbomify.com/CVE-2008-5329/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5090 and fix it if it is affected.

What it is: CVE-2007-5090 is a high-severity vulnerability in n/a, published on 26 Sep 2007. 
Exploitation: There is no known exploitation of CVE-2007-5090 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-2007-5090/ (Markdown: https://insights.sbomify.com/CVE-2007-5090/index.md)
```

## Sources

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

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