CVE-2009-1579: The map_yp_alias function in functions/imap_general.php in SquirrelMail before 1.4.18 and NaSMail before 1.7 allows remote attackers to…
Noroxi assessment
Priority: Monitor (action score 28/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: 3.3% (FIRST EPSS); higher than 89% of all records.
- Fixed version: squirrelmail (Debian:4.0) 2:1.4.9a-4; squirrelmail (Debian:5.0) 2:1.4.15-4+lenny1; squirrelmail (Red Hat:enterprise_linux:3::as) 0:1.4.8-13.el3.
Low priority for now. Upgrade to squirrelmail (Debian:4.0) 2:1.4.9a-4; squirrelmail (Debian:5.0) 2:1.4.15-4+lenny1; squirrelmail (Red Hat:enterprise_linux:3::as) 0:1.4.8-13.el3 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
The map_yp_alias function in functions/imap_general.php in SquirrelMail before 1.4.18 and NaSMail before 1.7 allows remote attackers to execute arbitrary commands via shell metacharacters in a username string that is used by the ypmatch program.
- Published
- May 14, 2009
- Updated
- Jun 16, 2026
- EPSS
- 3.3% · 89th percentile
- CWE
- CWE-94
Report tools
Action score
28
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.3%
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 squirrelmailall versions
- squirrelmail squirrelmailup to 1.4.17 inclusive
- squirrelmail squirrelmail0.1
- squirrelmail squirrelmail0.1.1
- squirrelmail squirrelmail0.1.2
- squirrelmail squirrelmail0.2
- squirrelmail squirrelmail0.2.1
- squirrelmail squirrelmail0.3
+12 more rows
- squirrelmail squirrelmail0.3.1
- squirrelmail squirrelmail0.3pre1
- squirrelmail squirrelmail0.3pre2
- squirrelmail squirrelmail0.4
- squirrelmail squirrelmail0.4pre1
- squirrelmail squirrelmail0.4pre2
- squirrelmail squirrelmail0.5
- squirrelmail squirrelmail0.5pre1
- squirrelmail squirrelmail0.5pre2
- squirrelmail squirrelmail1.0
- squirrelmail squirrelmail1.0.1
- squirrelmail squirrelmail1.0.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:4.0 | squirrelmail | before 2:1.4.9a-4 | 2:1.4.9a-4 |
| Debian:5.0 | squirrelmail | before 2:1.4.15-4+lenny1 | 2:1.4.15-4+lenny1 |
| Red Hat:enterprise_linux:3::as | squirrelmail | before 0:1.4.8-13.el3 | 0:1.4.8-13.el3 |
| Red Hat:enterprise_linux:4::as | squirrelmail | before 0:1.4.8-5.el4_8.5 | 0:1.4.8-5.el4_8.5 |
| Red Hat:enterprise_linux:5::client_workstation | squirrelmail | before 0:1.4.8-5.el5_3.7 | 0:1.4.8-5.el5_3.7 |
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-0030Jan 21, 2009 · A certain Red Hat patch for SquirrelMail 1.4.8 sets the same SQMSESSID cookie value for all sessions, which allows remote authenticated…27Monitor
- ← EarlierCVE-2009-1578May 14, 2009 · Multiple cross-site scripting (XSS) vulnerabilities in SquirrelMail before 1.4.18 and NaSMail before 1.7 allow remote attackers to inject…18Monitor
- Later →CVE-2009-1580May 14, 2009 · Session fixation vulnerability in SquirrelMail before 1.4.18 allows remote attackers to hijack web sessions via a crafted cookie.24Monitor
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.9a-4 · Debian:4.0 | Package registry (OSV) |
| red hat:squirrelmail | 0:1.4.8-13.el3 · Red Hat:enterprise_linux:3::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
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
AV:N/AC:M/Au:N/C:P/I:P/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.
Attack patterns (CAPEC)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- lists.apple.com/archives/security-announce/2010//Jun/msg00001.html
- secunia.com/advisories/35052
- secunia.com/advisories/35073
- secunia.com/advisories/35140
- secunia.com/advisories/35259
- secunia.com/advisories/37415
- secunia.com/advisories/40220
- squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/branches/SM-1_4-STABLE/squirrelmail/doc/ChangeLog
- squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/branches/SM-1_4-STABLE/squirrelmail/functions/imap_general.php?r1=13674&r2=13673&pathrev=13674
- squirrelmail.svn.sourceforge.net/viewvc/squirrelmail?view=rev&revision=13674
- support.apple.com/kb/HT4188
- www.debian.org/security/2009/dsa-1802
- www.mandriva.com/security/advisories?name=MDVSA-2009:110
- www.redhat.com/support/errata/RHSA-2009-1066.html
- www.securityfocus.com/bid/34916
- www.squirrelmail.org/security/issue/2009-05-10
- www.vupen.com/english/advisories/2009/1296
- www.vupen.com/english/advisories/2009/3315
- www.vupen.com/english/advisories/2010/1481
Vendor advisories and official records. Exploit/PoC links are deliberately left out.