# CVE-2006-6848: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands in ASPTicker via the admin interface, potentially compromising database integrity and confidentiality.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p5f6-24c7-fw7h

## What is CVE-2006-6848?

CVE-2006-6848 is a high-severity SQL injection vulnerability in n/a, published on 3 Jan 2007. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SQL injection vulnerability in admin.asp in ASPTicker 1.0 allows remote attackers to execute arbitrary SQL commands via the PATH_INFO, possibly related to the Password parameter.

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

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

It affects 1 product.


Products: Aspticker Aspticker.

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

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

## Is CVE-2006-6848 being exploited?

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

Public exploit code:

- ASPTicker 1.0 - Authentication Bypass (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6848 is a high-severity SQL injection vulnerability in n/a, published on 3 Jan 2007. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6848 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-2006-6848/ (Markdown: https://insights.sbomify.com/CVE-2006-6848/index.md)
```

## Sources

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

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