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…
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4% (FIRST EPSS); higher than 90.7% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: squirrelmail (Debian:5.0) 2:1.4.15-4+lenny3.1; squirrelmail (Red Hat:enterprise_linux:4::as) 0:1.4.8-18.el4; squirrelmail (Red Hat:enterprise_linux:5::client_workstation) 0:1.4.8-5.el5_7.13.
Low priority for now. Upgrade to squirrelmail (Debian:5.0) 2:1.4.15-4+lenny3.1; squirrelmail (Red Hat:enterprise_linux:4::as) 0:1.4.8-18.el4; squirrelmail (Red Hat:enterprise_linux:5::client_workstation) 0:1.4.8-5.el5_7.13 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 19, 2010
- Updated
- Jun 16, 2026
- EPSS
- 4.0% · 90th percentile
- CWE
- CWE-399
Report tools
Action score
21
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| squirrelmail | squirrelmail | cpe:2.3:a:squirrelmail:squirrelmail |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- squirrelmail squirrelmailup to 1.4.20 inclusive
- squirrelmail squirrelmail1.4
- squirrelmail squirrelmail1.4_rc1
- squirrelmail squirrelmail1.4.0
- squirrelmail squirrelmail1.4.0_rc1
- squirrelmail squirrelmail1.4.0_rc2a
- squirrelmail squirrelmail1.4.0-r1
- squirrelmail squirrelmail1.4.1
+12 more rows
- squirrelmail squirrelmail1.4.10
- squirrelmail squirrelmail1.4.10a
- squirrelmail squirrelmail1.4.11
- squirrelmail squirrelmail1.4.12
- squirrelmail squirrelmail1.4.13
- squirrelmail squirrelmail1.4.15
- squirrelmail squirrelmail1.4.15_rc1
- squirrelmail squirrelmail1.4.15rc1
- squirrelmail squirrelmail1.4.16
- squirrelmail squirrelmail1.4.17
- squirrelmail squirrelmail1.4.18
- squirrelmail squirrelmail1.4.19
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:5.0 | squirrelmail | before 2:1.4.15-4+lenny3.1 | 2:1.4.15-4+lenny3.1 |
| Red Hat:enterprise_linux:4::as | squirrelmail | before 0:1.4.8-18.el4 | 0:1.4.8-18.el4 |
| Red Hat:enterprise_linux:5::client_workstation | squirrelmail | before 0:1.4.8-5.el5_7.13 | 0:1.4.8-5.el5_7.13 |
Same product
squirrelmail: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-7692SquirrelMail 1.4.22 (and other versions before 20170427_0200-SVN) allows post-authentication remote code execution via a sendmail.cf file…45Plan
- CVE-2006-2842PHP remote file inclusion vulnerability in functions/plugin.php in SquirrelMail 1.4.6 and earlier, if register_globals is enabled and…44Plan
- CVE-2002-0516SquirrelMail 1.2.5 and earlier allows authenticated SquirrelMail users to execute arbitrary commands by modifying the THEME variable in a…43Plan
Published before and after this one in the same product
- ← EarlierCVE-2009-2964Aug 25, 2009 · Multiple cross-site request forgery (CSRF) vulnerabilities in SquirrelMail 1.4.19 and earlier, and NaSMail before 1.7, allow remote…27Monitor
- ← EarlierCVE-2010-1637Jun 22, 2010 · The Mail Fetch plugin in SquirrelMail 1.4.20 and earlier allows remote authenticated users to bypass firewall restrictions and use…27Monitor
- Later →CVE-2010-4554Jul 14, 2011 · functions/page_header.php in SquirrelMail 1.4.21 and earlier does not prevent page rendering inside a frame in a third-party HTML document…18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:squirrelmail | 2:1.4.15-4+lenny3.1 · Debian:5.0 | Package registry (OSV) |
| red hat:squirrelmail | 0:1.4.8-18.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
CWE-399 · Resource Management ErrorsCVSS vector
AV:N/AC:L/Au:N/C:N/I:N/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (14 more)Show less
- lists.fedoraproject.org/pipermail/package-announce/2010-August/045372.html
- lists.fedoraproject.org/pipermail/package-announce/2010-August/045383.html
- rhn.redhat.com/errata/RHSA-2012-0103.html
- secunia.com/advisories/40964
- secunia.com/advisories/40971
- squirrelmail.org/security/issue/2010-07-23
- squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/branches/SM-1_4-STABLE/squirrelmail/functions/imap_general.php?view=patch&r1=13972&r2=13971&pathrev=13972
- support.apple.com/kb/HT5130
- www.debian.org/security/2010/dsa-2091
- www.securityfocus.com/bid/42399
- www.vupen.com/english/advisories/2010/2070
- www.vupen.com/english/advisories/2010/2080
- bugzilla.redhat.com/show_bug.cgi?id=618096
- exchange.xforce.ibmcloud.com/vulnerabilities/61124
Vendor advisories and official records. Exploit/PoC links are deliberately left out.