# CVE-2006-6282: Information disclosure in n/a

> Remote attackers can trigger SQL errors in Vikingboard to potentially disclose sensitive information if error display is enabled.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-43hc-w5c7-2rx7

## What is CVE-2006-6282?

CVE-2006-6282 is a critical vulnerability in n/a, published on 4 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

members.php in Vikingboard 0.1.2 allows remote attackers to trigger a forced SQL error via an invalid s parameter, a different vector than CVE-2006-4709.  NOTE: might only be an exposure if display_errors is enabled, but due to lack of details, even this is not clear.

## Which versions are affected by CVE-2006-6282?

It affects 1 product.


Products: Vikingboard Vikingboard.

## How do I fix CVE-2006-6282?

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

## Is CVE-2006-6282 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6284](https://insights.sbomify.com/CVE-2006-6284/): Path traversal in n/a (critical 9.0)
- [CVE-2006-4708](https://insights.sbomify.com/CVE-2006-4708/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2006-4709](https://insights.sbomify.com/CVE-2006-4709/): SQL injection in n/a (medium 5.0)
- [CVE-2007-4088](https://insights.sbomify.com/CVE-2007-4088/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2007-4089](https://insights.sbomify.com/CVE-2007-4089/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6282 and fix it if it is affected.

What it is: CVE-2006-6282 is a critical vulnerability in n/a, published on 4 Dec 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-6282 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-2006-6282/ (Markdown: https://insights.sbomify.com/CVE-2006-6282/index.md)
```

## Sources

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

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