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

> Remote attackers could potentially execute arbitrary SQL commands via the UpdateID0 parameter in VPMi Enterprise, though the vendor disputes this vulnerability.

- **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 needed
- **Fix available:** No
- **Published:** 25 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xf8m-ppqx-36p7

## What is CVE-2006-0897?

CVE-2006-0897 is a high-severity SQL injection vulnerability in n/a, published on 25 Feb 2006. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in VCS Virtual Program Management Intranet (VPMi) Enterprise 3.3 allows remote attackers to execute arbitrary SQL commands via the UpdateID0 parameter to Service_Requests.asp.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.  NOTE: the vendor has disputed this issue, saying that "[we] have a behind the scenes complex state management system that uses a combination of keys placed in JavaScript and Session State (server side) that protects against the type of SQL injection you describe.  We have tested for many of the cases and have not found it to be an issue."  Further investigation suggests that the original researcher might have triggered errors using invalid field values, which is not proof of SQL injection; however, the vendor did not receive a response from the original researcher

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

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

It affects 1 product.


Products: Virtual Communication Services Vpmi Enterprise.

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

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

## Is CVE-2006-0897 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-1266](https://insights.sbomify.com/CVE-2006-1266/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0897 is a high-severity SQL injection vulnerability in n/a, published on 25 Feb 2006. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0897 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-0897/ (Markdown: https://insights.sbomify.com/CVE-2006-0897/index.md)
```

## Sources

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

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