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

> Remote attackers can execute arbitrary SQL commands in Zoph, potentially reading or modifying database contents.

- **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:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 27 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-6837, GHSA-g67w-cmqc-xp9h

## What is CVE-2008-6837?

CVE-2008-6837 is a high-severity SQL injection vulnerability in n/a, published on 27 Jun 2009. It can be exploited over the network.

### Official description

SQL injection vulnerability in Zoph 0.7.2.1 allows remote attackers to execute arbitrary SQL commands via unspecified vectors, a different issue than CVE-2008-3258.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

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

It affects 1 product.


Products: Zoph Zoph.

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

Upgrade to a fixed version.

## Is CVE-2008-6837 being exploited?

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

Public exploit code:

- Zoph 0.7.2.1 - SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-3258](https://insights.sbomify.com/CVE-2008-3258/): SQL injection in n/a (high 7.5)
- [CVE-2007-3905](https://insights.sbomify.com/CVE-2007-3905/): SQL injection in n/a (high 7.5)
- [CVE-2014-9235](https://insights.sbomify.com/CVE-2014-9235/): SQL injection in n/a (medium 6.5)
- [CVE-2014-9236](https://insights.sbomify.com/CVE-2014-9236/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2009-2343](https://insights.sbomify.com/CVE-2009-2343/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6837 is a high-severity SQL injection vulnerability in n/a, published on 27 Jun 2009. It can be exploited over the network.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6837 exists.

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

## Sources

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

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