Skip to content
Fencer Intel
critical 9.3

CVE-2010-0816 in the critical feed json

Integer overflow in inetcomm.dll in Microsoft Outlook Express 5.5 SP2, 6, and 6 SP1; Windows Live Mail on Windows XP SP2 and SP3, Windows V…

published 16y ago modified 4mo ago also EUVD-2010-0842

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
20.3%
EPSS 20.3% chance of exploitation in 30 days, percentile 97%
public exploits
1
Exploit-DB

Summary

Integer overflow in inetcomm.dll in Microsoft Outlook Express 5.5 SP2, 6, and 6 SP1; Windows Live Mail on Windows XP SP2 and SP3, Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7; and Windows Mail on Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7 allows remote e-mail servers and man-in-the-middle attackers to execute arbitrary code via a crafted (1) POP3 or (2) IMAP response, as demonstrated by a certain +OK response on TCP port 110, aka "Outlook Express and Windows Mail Integer Overflow Vulnerability."

Is CVE-2010-0816 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (EDB-12564)
  2. Published

Exploit prediction

20.33% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-12564 Microsoft Windows Outlook Express and Windows Mail - Integer Overflow dos, 2010-05-11
  • protekresearchlab.com http://www.protekresearchlab.com/index.php?option=com_content&view=article&id=13&Itemid=13 referenced PoC, tagged "exploit" by a source, unverified
  • archives.neohapsis.com http://archives.neohapsis.com/archives/bugtraq/2010-05/0068.html referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/40052 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness

References

Sources

Fencer Intel 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.