Imap vulnerabilitiesRanked by how likely they are to be used.

Product43 versions
The short answer

Imap is made by University of Washington. We track 7 published vulnerabilities listed under that exact name, across 43 versions. None of them is on the list of flaws known to be exploited today. University of Washington lists newer releases under their own names, such as Imap Toolkit, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Imap listed under other names? Yes.

University of Washington also lists Imap under more specific names, such as Imap Toolkit. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Known exploited

Which Imap vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Imap's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Imap flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 68%

    Buffer overflow in University of Washington imapd version 4.7 allows users with a valid account to execute commands via LIST or other commands.

    CVSS7.5Published16 Apr 2000
  2. 32%

    Buffer overflow in the pop-2d POP daemon in the IMAP package allows remote attackers to gain privileges via the FOLD command.

    CVSS10.0Published26 May 1999
  3. 18%

    Arbitrary command execution via IMAP buffer overflow in authenticate command.

    CVSS10.0Published20 Jul 1998
  4. 13%

    Buffer overflow in University of Washington's implementation of IMAP and POP servers.

    CVSS10.0Published7 Apr 1997
  5. 2.5%

    Buffer overflow in University of Washington c-client library (used by pine and other programs) allows remote attackers to execute arbitrary commands via a long X-Keywords header.

    CVSS7.5Published14 Nov 2000
  6. 1.8%

    Off-by-one error in the rfc822_output_char function in the RFC822BUFFER routines in the University of Washington (UW) c-client library, as used by the UW IMAP toolkit before imap-2007e and other applications, allows...

    CVSS4.3Published23 Dec 2008
  7. 0.3%

    POP2 or POP3 server (pop3d) in imap-uw IMAP package on FreeBSD and other operating systems creates lock files with predictable names, which allows local users to cause a denial of service (lack of mail access) for...

    CVSS2.1Published31 Aug 2001
Precursor Intelligence

Running Imap? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 7 published vulnerabilities listed under the name Imap, across 43 versions.

None of Imap's vulnerabilities is on the list of flaws known to be exploited today.

University of Washington also lists Imap under more specific names, such as Imap Toolkit. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a Precursor Intelligence account and track Imap. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.