CVE-2010-2813

CVE-2010-2813 is a medium-severity vulnerability in Squirrelmail with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-399.

Key facts

Description

functions/imap_general.php in SquirrelMail before 1.4.21 does not properly handle 8-bit characters in passwords, which allows remote attackers to cause a denial of service (disk consumption) by making many IMAP login attempts with different usernames, leading to the creation of many preferences files.

Frequently asked questions

What is CVE-2010-2813?
functions/imap_general.php in SquirrelMail before 1.4.21 does not properly handle 8-bit characters in passwords, which allows remote attackers to cause a denial of service (disk consumption) by making many IMAP login attempts with different usernames, leading to the creation of many preferences files.
How severe is CVE-2010-2813?
CVE-2010-2813 has a CVSS 2.0 base score of 5.0, rated medium severity.
Is CVE-2010-2813 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (89th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2010-2813?
CVE-2010-2813 primarily affects Squirrelmail. In total, 54 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2010-2813?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2010-2813 published?
CVE-2010-2813 was published on 2010-08-19 and last updated on 2026-06-16.

References

Affected products (54)

More vulnerabilities in Squirrelmail

All CVEs affecting Squirrelmail →

Other CWE-399 (Resource Management Errors) vulnerabilities

Browse all CWE-399 (Resource Management Errors) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: