# CVE-2005-4515: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via search parameters in WebDB, 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:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mfrc-8wqr-f298

## What is CVE-2005-4515?

CVE-2005-4515 is a high-severity SQL injection vulnerability in n/a, published on 23 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in WebDB 1.1 and earlier allows remote attackers to execute arbitrary SQL commands via unspecified search parameters, possibly Search0.  NOTE: the vendor has disputed this issue, saying that "WebDB is a generic online database system used by many of the clients of Lois Software. The flaw that was identified was some code that was added for a client to do some testing of his system and only certain safe commands were allowed. This code has now been removed and it is not now possible to use SQL queries as part of the query string.  No installation or patch is required All clients use a common code library and have their own front end and databases and connections. So as soon as a change / upgrade / enhancement is made to the code, all users of the software begin to use the latest changes immediately."  Since the issue appeared in a custom web site and no action is required on the part of customers, this issue should not be included in CVE

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

## Which versions are affected by CVE-2005-4515?

It affects 1 product.


Products: Lois Software Webdb.

## How do I fix CVE-2005-4515?

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

## Is CVE-2005-4515 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4515 and fix it if it is affected.

What it is: CVE-2005-4515 is a high-severity SQL injection vulnerability in n/a, published on 23 Dec 2005. 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-2005-4515 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-2005-4515/ (Markdown: https://insights.sbomify.com/CVE-2005-4515/index.md)
```

## Sources

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

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