# CVE-2005-4713: Denial of service in n/a

> Remote attackers can cause a denial of service via segmentation fault in PAM-MySQL's SQL logging facility when used with vsftpd.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-4713, GHSA-c4xx-wp4h-934r

## What is CVE-2005-4713?

CVE-2005-4713 is a medium-severity denial of service vulnerability in n/a, published on 13 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in the SQL logging facility in PAM-MySQL 0.6.x before 0.6.2 and 0.7.x before 0.7pre3 allows remote attackers to cause a denial of service (segmentation fault) via unspecified vectors, probably involving the pam_mysql_sql_log function when being used in vsftpd, which does not include the IP address argument to an sprintf call.

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

It affects 1 product.


Products: Pam Mysql Pam Mysql.

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

Upgrade to a fixed version.

## Is CVE-2005-4713 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-0957](https://insights.sbomify.com/CVE-2000-0957/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-4713 is a medium-severity denial of service vulnerability in n/a, published on 13 Feb 2006. 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-4713 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-4713/ (Markdown: https://insights.sbomify.com/CVE-2005-4713/index.md)
```

## Sources

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

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