CVE-2002-0389
Summary
| CVE | CVE-2002-0389 |
|---|---|
| State | PUBLISHED |
| Assigner | mitre |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2002-06-18 04:00:00 UTC |
| Updated | 2025-04-03 01:03:51 UTC |
| Description | Pipermail in Mailman stores private mail messages with predictable filenames in a world-executable directory, which allows local users to read private mailing list archives. |
Risk And Classification
Primary CVSS: v2.0 2.1 from [email protected]
AV:L/AC:L/Au:N/C:P/I:N/A:N
Problem Types: NVD-CWE-Other | n/a
CVSS v2.0 Breakdown
Access Vector
LocalAccess Complexity
LowAuthentication
NoneConfidentiality
PartialIntegrity
NoneAvailability
NoneAV:L/AC:L/Au:N/C:P/I:N/A:N
NVD Known Affected Configurations (CPE 2.3)
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Mailman / Bugs / #384 SECURITY: Pipermail permissions problem | af854a3a-2127-422b-91ae-364da2661108 | sourceforge.net | |
| Red Hat Customer Portal | af854a3a-2127-422b-91ae-364da2661108 | rhn.redhat.com | |
| Pipermail/Mailman Insecure Archives Permissions Vulnerability | af854a3a-2127-422b-91ae-364da2661108 | www.securityfocus.com | |
| 'Mailman/Pipermail private mailing list/local user vulnerability' - MARC | af854a3a-2127-422b-91ae-364da2661108 | marc.info | |
| ISS X-Force Database: pipermail-view-archives (8874): Pipermail could allow an attacker to view private mailing list archives | af854a3a-2127-422b-91ae-364da2661108 | www.iss.net | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
| Organization | Published | Contributor | Statement |
|---|---|---|---|
| Red Hat | 2016-12-27 | Joshua Bressers | Red Hat does not intend to take any action on this issue. This is the expected behavior of Mailman and is not considered to be a security flaw by upstream. If Mailman upstream addresses this issue in a future update, we may revisit our decision. |
There are currently no legacy QID mappings associated with this CVE.