Skip to content
Fencer Intel
medium 5.8

CVE-2011-2752 json

CRLF injection vulnerability in SquirrelMail 1.4.21 and earlier allows remote attackers to modify or add preference values via a \n (newlin…

published 15y ago modified 4mo ago also EUVD-2011-2727

cvss
5.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

CRLF injection vulnerability in SquirrelMail 1.4.21 and earlier allows remote attackers to modify or add preference values via a \n (newline) character, a different vulnerability than CVE-2010-4555.

Patch / fix

  • squirrelmail RHEL 4 1.4.8-18.el4
  • squirrelmail RHEL 5 1.4.8-5.el5_7.13

red hat advisories RHSA-2012:0103

Is CVE-2011-2752 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-2752 updated cvss 4.3

SquirrelMail: CRLF injection vulnerability

  • Red Hat Enterprise Linux (v. 5 server) squirrelmail 1.4.8-5.el5_7.13 Red Hat Enterprise Linux AS version 4 squirrelmail 1.4.8-18.el4 Red Hat Enterprise Linux Desktop version 4 squirrelmail 1.4.8-18.el4 Red Hat Enterprise Linux ES version 4 squirrelmail 1.4.8-18.el4 Red Hat Enterprise Linux WS version 4 squirrelmail 1.4.8-18.el4 Red Hat RHEL Desktop Workstation (v. 5 client) squirrelmail 1.4.8-5.el5_7.13
    fixed: vendor fix RHSA-2012:0103

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

CVSS scores

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

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

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.