# CVE-2008-6992: Security feature bypass in n/a

> Remote attackers can bypass GreenSQL Firewall's SQL injection protection using specific WHERE clause expressions, allowing unauthorized database access.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m57q-qwrv-4p2p

## What is CVE-2008-6992?

CVE-2008-6992 is a high-severity vulnerability in n/a, published on 18 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GreenSQL Firewall (greensql-fw), possibly before 0.9.2 or 0.9.4, allows remote attackers to bypass the SQL injection protection mechanism via a WHERE clause containing an expression such as "x=y=z", which is successfully parsed by MySQL.

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

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

It affects 1 product.


Products: Greensql Greensql Firewall.

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

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

## Is CVE-2008-6992 being exploited?

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

Public exploit code:

- GreenSQL Firewall 0.9.x - WHERE Clause Security Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-7229](https://insights.sbomify.com/CVE-2008-7229/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6992 is a high-severity vulnerability in n/a, published on 18 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6992 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-6992/ (Markdown: https://insights.sbomify.com/CVE-2008-6992/index.md)
```

## Sources

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

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