CVE-2007-1373 in the critical feed json
Stack-based buffer overflow in Mercury/32 (aka Mercury Mail Transport System) 4.01b and earlier allows remote attackers to execute arbitrar…
published 2007-03-10 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-1369
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 60.2%
- EPSS 60.2% chance of exploitation in 30 days, percentile 99.1%
- public exploits
- 4
- Metasploit, Exploit-DB
Summary
Stack-based buffer overflow in Mercury/32 (aka Mercury Mail Transport System) 4.01b and earlier allows remote attackers to execute arbitrary code via a long LOGIN command. NOTE: this might be the same issue as CVE-2006-5961.
Timeline
- First public exploit (EDB-1223)
- Published
Exploit prediction
60.23% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/windows/imap/mercury_login Mercury/32 4.01 IMAP LOGIN SEH Buffer Overflow metasploit exploit, normal rank, 2007-03-06
- EDB-16473 Mercury/32 Mail Server < 4.01b - LOGIN Buffer Overflow (Metasploit) remote, 2010-06-22
- EDB-3418 Mercury/32 Mail Server 4.01b - 'check' Buffer Overflow (PoC) dos, 2007-03-06
- EDB-1223 Mercury/32 Mail Server 4.01a (Pegasus) - IMAP Buffer Overflow remote, 2005-09-20
- lists.grok.org.uk http://lists.grok.org.uk/pipermail/full-disclosure/2007-March/052802.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
References
-
lists.grok.org.uk
/pipermail/full-disclosure/2007-March/052802.html
mailing-list, exploit
-
secunia.com
/advisories/24367
third-party-advisory, vendor-advisory
-
osvdb.org
/33883
vdb-entry
-
securityreason.com
/securityalert/2398
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/32848
vdb-entry
Sources
- CVE List CVE-2007-1373
- NVD CVE-2007-1373
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.