CVE-2004-0884: The (1) libsasl and (2) libsasl2 libraries in Cyrus-SASL 2.1.18 and earlier trust the SASL_PATH environment variable to find all available…
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.50% (FIRST EPSS).
- No special conditions are required; it is repeatable.
- Fixed version: cyrus-sasl2 (Debian:12) 2.1.19-1.3; cyrus-sasl (Debian:3.0) 1.5.27-3.1woody5; cyrus-sasl-mit (Debian:3.0) 1.5.24-15woody3.
Low priority for now. Upgrade to cyrus-sasl2 (Debian:12) 2.1.19-1.3; cyrus-sasl (Debian:3.0) 1.5.27-3.1woody5; cyrus-sasl-mit (Debian:3.0) 1.5.24-15woody3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The (1) libsasl and (2) libsasl2 libraries in Cyrus-SASL 2.1.18 and earlier trust the SASL_PATH environment variable to find all available SASL plug-ins, which allows local users to execute arbitrary code by modifying the SASL_PATH to point to malicious programs.
- Published
- Jan 27, 2005
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 43th percentile
- CWE
- —
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- conectiva linux10.0
- conectiva linux9.0
- cyrus sasl1.5.24
- cyrus sasl1.5.27
- cyrus sasl1.5.28
- cyrus sasl2.1.10
- cyrus sasl2.1.11
- cyrus sasl2.1.12
+8 more rows
- cyrus sasl2.1.13
- cyrus sasl2.1.14
- cyrus sasl2.1.15
- cyrus sasl2.1.16
- cyrus sasl2.1.17
- cyrus sasl2.1.18
- cyrus sasl2.1.18_r1
- cyrus sasl2.1.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | cyrus-sasl2 | before 2.1.19-1.3 | 2.1.19-1.3 |
| Debian:3.0 | cyrus-sasl | before 1.5.27-3.1woody5 | 1.5.27-3.1woody5 |
| Debian:3.0 | cyrus-sasl-mit | before 1.5.24-15woody3 | 1.5.24-15woody3 |
| Red Hat:enterprise_linux:3::as | cyrus-sasl | before 0:2.1.15-10 | 0:2.1.15-10 |
| Red Hat:enterprise_linux:3::as | cyrus-sasl-debuginfo | before 0:2.1.15-10 | 0:2.1.15-10 |
| Red Hat:enterprise_linux:3::as | cyrus-sasl-devel | before 0:2.1.15-10 | 0:2.1.15-10 |
| Red Hat:enterprise_linux:3::as | cyrus-sasl-gssapi | before 0:2.1.15-10 | 0:2.1.15-10 |
| Red Hat:enterprise_linux:3::as | cyrus-sasl-md5 | before 0:2.1.15-10 | 0:2.1.15-10 |
| Red Hat:enterprise_linux:3::as | cyrus-sasl-plain | before 0:2.1.15-10 | 0:2.1.15-10 |
Same product
cyrus: all recordsOther highest-scoring records for the same primary product.
- CVE-2005-0373Buffer overflow in digestmd5.c CVS release 1.170 (also referred to as digestmda5.c), as used in the DIGEST-MD5 SASL plugin for Cyrus-SASL…31Monitor
- CVE-2002-2043SQL injection vulnerability in the LDAP and MySQL authentication patch for Cyrus SASL 1.5.24 and 1.5.27 allows remote attackers to execute…30Monitor
- CVE-2006-1721digestmd5.c in the CMU Cyrus Simple Authentication and Security Layer (SASL) library 2.1.18, and possibly other versions before 2.1.21…11Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:cyrus-sasl | 1.5.27-3.1woody5 · Debian:3.0 | Package registry (OSV) |
| debian:cyrus-sasl-mit | 1.5.24-15woody3 · Debian:3.0 | Package registry (OSV) |
| debian:cyrus-sasl2 | 2.1.19-1.3 · Debian:12 | Package registry (OSV) |
| red hat:cyrus-sasl | 0:2.1.15-10 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:cyrus-sasl-debuginfo | 0:2.1.15-10 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:cyrus-sasl-devel | 0:2.1.15-10 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:cyrus-sasl-gssapi | 0:2.1.15-10 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:cyrus-sasl-md5 | 0:2.1.15-10 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:cyrus-sasl-plain | 0:2.1.15-10 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
—
CVSS vector
AV:L/AC:L/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (13 more)Show less
- lists.apple.com/archives/security-announce/2005/Mar/msg00000.html
- marc.info/?l=bugtraq&m=110693126007214&w=2
- rhn.redhat.com/errata/RHSA-2004-546.html
- www.ciac.org/ciac/bulletins/p-003.shtml
- www.debian.org/security/2004/dsa-563
- www.debian.org/security/2004/dsa-568
- www.gentoo.org/security/en/glsa/glsa-200410-05.xml
- www.mandriva.com/security/advisories?name=MDKSA-2004:106
- www.securityfocus.com/bid/11347
- www.trustix.net/errata/2004/0053/
- bugzilla.fedora.us/show_bug.cgi?id=2137
- exchange.xforce.ibmcloud.com/vulnerabilities/17643
- oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11678
Vendor advisories and official records. Exploit/PoC links are deliberately left out.