CVE-2003-1367

NONECVSS 0.0

0.0

The which_access variable for Majordomo 2.0 through 1.94.4, and possibly earlier versions, is set to "open" by default, which allows remote attackers to identify the email addresses of members of mailing lists via a "which" command.

CVSS v3: —
EG Score: —
EPSS: 57.2%
KEV: Not listed

Published

December 31, 2003

Last Modified

April 16, 2026

References (8)

cve@mitrehttp://securityreason.com/securityalert/3235
cve@mitrehttp://www.securityfocus.com/archive/1/310113
cve@mitrehttp://www.securityfocus.com/bid/6761
cve@mitrehttps://exchange.xforce.ibmcloud.com/vulnerabilities/11243
af854a3a-2127-422b-91ae-364da2661108http://securityreason.com/securityalert/3235
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/archive/1/310113
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/6761
af854a3a-2127-422b-91ae-364da2661108https://exchange.xforce.ibmcloud.com/vulnerabilities/11243

Data Freshness Timeline

(refreshed 12× in last 7d / 17× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-29 13:40 UTCepss_batch
2026-05-29 13:40 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:37 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-24 16:42 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-20 22:36 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-18 21:29 UTCepss_batch
2026-05-18 21:29 UTCepss_batch

Frequently asked(4)

What is CVE-2003-1367?

CVE-2003-1367 is a none vulnerability published on December 31, 2003. The which_access variable for Majordomo 2.0 through 1.94.4, and possibly earlier versions, is set to "open" by default, which allows remote attackers to identify the email addresses of members of mailing lists via a "which" command.

When was CVE-2003-1367 disclosed?

CVE-2003-1367 was first published in the National Vulnerability Database on December 31, 2003, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2003-1367 actively exploited?

CVE-2003-1367 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 57.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2003-1367?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2003-1367, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2003-1367

Explore →

Is Your Infrastructure Affected by CVE-2003-1367?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2003-1367

📅 Published

🔄 Last Modified

🔗 References (8)