cve.bz

CVE-2004-1143 gnu mailman

no score yetEPSS 1.6%Fix available

gnu mailman: no CVSS score yet. EPSS 1.6% estimated probability of exploitation activity in the next 30 days.

The password generation in mailman before 2.1.5 generates only 5 million unique passwords, which makes it easier for remote attackers to guess passwords via a brute force attack.
EPSS
1.6% (unchanged from 1.6% a week ago; 1.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 77th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2004-1143 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2004-1143?via=ask-ai-copy and https://cve.bz/cve/CVE-2004-1143?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2004-1143 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
gnu:mailman1.0
gnu:mailman1.1
gnu:mailman2.0
gnu:mailman2.0:beta3
gnu:mailman2.0:beta4
gnu:mailman2.0:beta5
gnu:mailman2.0.1
gnu:mailman2.0.2
gnu:mailman2.0.3
gnu:mailman2.0.4
gnu:mailman2.0.5
gnu:mailman2.0.6
gnu:mailman2.0.7
gnu:mailman2.0.8
gnu:mailman2.0.9
gnu:mailman2.0.10
gnu:mailman2.0.11
gnu:mailman2.0.12
gnu:mailman2.0.13
gnu:mailman2.1
gnu:mailman2.1.1
gnu:mailman2.1.2
gnu:mailman2.1.3
gnu:mailman2.1.4
gnu:mailman2.1b1

References

Check your stackJSON