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

> Authenticated attackers can execute arbitrary SQL commands via specific configuration entries in the FreeRADIUS SQL module.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-1454, GHSA-vpgg-jj2h-wmwf

## What is CVE-2005-1454?

CVE-2005-1454 is a high-severity SQL injection vulnerability in n/a, published on 19 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in the radius_xlat function in the SQL module for FreeRADIUS 1.0.2 and earlier allows remote authenticated users to execute arbitrary SQL commands via (1) group_membership_query, (2) simul_count_query, or (3) simul_verify_query configuration entries.

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

It affects 1 product.


Products: Freeradius Freeradius.

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

Upgrade to a fixed version.

## Is CVE-2005-1454 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-10979](https://insights.sbomify.com/CVE-2017-10979/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-10984](https://insights.sbomify.com/CVE-2017-10984/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9148](https://insights.sbomify.com/CVE-2017-9148/): Auth bypass in n/a (critical 9.8)
- [CVE-2015-8763](https://insights.sbomify.com/CVE-2015-8763/): Memory corruption in n/a (high 8.1)
- [CVE-2015-8764](https://insights.sbomify.com/CVE-2015-8764/): Memory corruption in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1454 is a high-severity SQL injection vulnerability in n/a, published on 19 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-1454 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-1454/ (Markdown: https://insights.sbomify.com/CVE-2005-1454/index.md)
```

## Sources

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

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