# CVE-2006-1721: Denial of service in n/a > Remote unauthenticated attackers can cause a denial of service via malformed inputs in DIGEST-MD5 negotiation within the Cyrus SASL library. - **Severity:** Low 2.6 (`AV:N/AC:H/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:** 11 Apr 2006 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2006-1721, DSA-1042-1, GHSA-x5mm-w7g6-r6fq, RHSA-2007:0795, RHSA-2007:0878 ## What is CVE-2006-1721? CVE-2006-1721 is a low-severity denial of service vulnerability in n/a, published on 11 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description digestmd5.c in the CMU Cyrus Simple Authentication and Security Layer (SASL) library 2.1.18, and possibly other versions before 2.1.21, allows remote unauthenticated attackers to cause a denial of service (segmentation fault) via malformed inputs in DIGEST-MD5 negotiation. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2006-1721? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `cyrus-sasl` | Red Hat:enterprise_linux:3::as | All versions | 0:2.1.15-15 | | `cyrus-sasl-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:2.1.15-15 | | `cyrus-sasl-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:2.1.15-15 | | `cyrus-sasl-gssapi` | Red Hat:enterprise_linux:3::as | All versions | 0:2.1.15-15 | | `cyrus-sasl-md5` | Red Hat:enterprise_linux:3::as | All versions | 0:2.1.15-15 | | `cyrus-sasl-plain` | Red Hat:enterprise_linux:3::as | All versions | 0:2.1.15-15 | | `cyrus-sasl` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.1.15-15 | | `cyrus-sasl-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.1.15-15 | | `cyrus-sasl-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.1.15-15 | | `cyrus-sasl-gssapi` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.1.15-15 | | `cyrus-sasl-md5` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.1.15-15 | | `cyrus-sasl-plain` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.1.15-15 | | `cyrus-sasl` | Red Hat:enterprise_linux:3::es | All versions | 0:2.1.15-15 | | `cyrus-sasl-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:2.1.15-15 | | `cyrus-sasl-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:2.1.15-15 | | `cyrus-sasl-gssapi` | Red Hat:enterprise_linux:3::es | All versions | 0:2.1.15-15 | | `cyrus-sasl-md5` | Red Hat:enterprise_linux:3::es | All versions | 0:2.1.15-15 | | `cyrus-sasl-plain` | Red Hat:enterprise_linux:3::es | All versions | 0:2.1.15-15 | | `cyrus-sasl` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.1.15-15 | | `cyrus-sasl-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.1.15-15 | | `cyrus-sasl-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.1.15-15 | | `cyrus-sasl-gssapi` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.1.15-15 | | `cyrus-sasl-md5` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.1.15-15 | | `cyrus-sasl-plain` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.1.15-15 | | `cyrus-sasl` | Red Hat:enterprise_linux:4::as | All versions | 0:2.1.19-14 | | `cyrus-sasl-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.1.19-14 | | `cyrus-sasl-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.1.19-14 | | `cyrus-sasl-gssapi` | Red Hat:enterprise_linux:4::as | All versions | 0:2.1.19-14 | | `cyrus-sasl-md5` | Red Hat:enterprise_linux:4::as | All versions | 0:2.1.19-14 | | `cyrus-sasl-ntlm` | Red Hat:enterprise_linux:4::as | All versions | 0:2.1.19-14 | | `cyrus-sasl-plain` | Red Hat:enterprise_linux:4::as | All versions | 0:2.1.19-14 | | `cyrus-sasl-sql` | Red Hat:enterprise_linux:4::as | All versions | 0:2.1.19-14 | | `cyrus-sasl` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.1.19-14 | | `cyrus-sasl-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.1.19-14 | | `cyrus-sasl-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.1.19-14 | | `cyrus-sasl-gssapi` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.1.19-14 | | `cyrus-sasl-md5` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.1.19-14 | | `cyrus-sasl-ntlm` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.1.19-14 | | `cyrus-sasl-plain` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.1.19-14 | | `cyrus-sasl-sql` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.1.19-14 | Products: Cyrus Sasl. ## How do I fix CVE-2006-1721? Upgrade to a fixed version. ## Is CVE-2006-1721 being exploited? There is no known exploitation of CVE-2006-1721 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2002-2043](https://insights.sbomify.com/CVE-2002-2043/): SQL injection in n/a (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2006-1721 and fix it if it is affected. What it is: CVE-2006-1721 is a low-severity denial of service vulnerability in n/a, published on 11 Apr 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-2006-1721 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-1721/ (Markdown: https://insights.sbomify.com/CVE-2006-1721/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2006-1721 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-1721 - OSV: https://osv.dev/vulnerability/CVE-2006-1721 --- From sbomify Insights: https://insights.sbomify.com/CVE-2006-1721/ Summaries are generated and may contain mistakes; the official description above is the record.