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

> Remote attackers can inject SQL commands via whitespace manipulation in the orderby parameter, potentially reading or modifying database contents.

- **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:** 10 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9fpm-9892-q4hp

## What is CVE-2005-4144?

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

### Official description

Lyris ListManager 5.0 through 8.9a allows remote attackers to add "ORDER BY" columns to SQL queries via unusual whitespace characters in the orderby parameter, such as (1) newlines and (2) 0xFF (ASCII 255) characters, which are interpreted as whitespace.

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

It affects 1 product.


Products: Lyris List Manager.

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

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

## Is CVE-2005-4144 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6319](https://insights.sbomify.com/CVE-2007-6319/): Privilege escalation in n/a (critical 10.0)
- [CVE-2005-4143](https://insights.sbomify.com/CVE-2005-4143/): SQL injection in n/a (high 7.5)
- [CVE-2006-4546](https://insights.sbomify.com/CVE-2006-4546/): Privilege escalation in n/a (medium 6.5)
- [CVE-2006-4547](https://insights.sbomify.com/CVE-2006-4547/): Information disclosure in n/a (medium 6.5)
- [CVE-2000-0758](https://insights.sbomify.com/CVE-2000-0758/): Auth bypass in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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