CVE-2006-4624
published 2006-09-07CVE-2006-4624: CRLF injection vulnerability in Utils.py in Mailman before 2.1.9rc1 allows remote attackers to spoof messages in the error log and possibly trick the…
PriorityP415low2.6CVSS 2.0
AVNACHAuNCNIPAN
EPSS
2.75%
84.7th percentile
CRLF injection vulnerability in Utils.py in Mailman before 2.1.9rc1 allows remote attackers to spoof messages in the error log and possibly trick the administrator into visiting malicious URLs via CRLF sequences in the URI.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| gnu | mailman | <= 2.1.8 | — |
CVSS provenance
nvdv2.02.6LOWAV:N/AC:H/Au:N/C:N/I:P/A:N
vendor_redhat2.6LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-pr3g-gx73-r4cm: CRLF injection vulnerability in Utils
ghsa_unreviewed·2022-05-01
CVE-2006-4624 [LOW] CWE-94 GHSA-pr3g-gx73-r4cm: CRLF injection vulnerability in Utils
CRLF injection vulnerability in Utils.py in Mailman before 2.1.9rc1 allows remote attackers to spoof messages in the error log and possibly trick the administrator into visiting malicious URLs via CRLF sequences in the URI.
Red Hat
mailman logfile CRLF injection
vendor_redhat·2006-06-23·CVSS 2.6
CVE-2006-4624 [LOW] mailman logfile CRLF injection
mailman logfile CRLF injection
CRLF injection vulnerability in Utils.py in Mailman before 2.1.9rc1 allows remote attackers to spoof messages in the error log and possibly trick the administrator into visiting malicious URLs via CRLF sequences in the URI.
Statement: The Red Hat Product Security has rated this issue as having low security impact and expects to release a future update to address this flaw. More information regarding issue severity can be found here:
https://access.redhat.com/security/updates/classification/
The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 2.1 and 3 which are in maintenance mode.
This bug will be addressed in a future update of Red Hat
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2006-4624 mailman 2.1.9 needed (CVE-2006-3636 CVE-2006-2941)
bugzilla·2006-10-20·CVSS 5.0
CVE-2006-4624 [MEDIUM] CVE-2006-4624 mailman 2.1.9 needed (CVE-2006-3636 CVE-2006-2941)
CVE-2006-4624 mailman 2.1.9 needed (CVE-2006-3636 CVE-2006-2941)
+++ This bug was initially created as a clone of Bug #209891 +++
Cloning for FC3.
+++ This bug was initially created as a clone of Bug #206607 +++
FC6 needs mailman 2.1.9 to correct CVE-2006-4624, CVE-2006-3636, CVE-2006-2941
This bug is for FC3 and FC4. Upgrading to mailman 2.1.9 will correct these
vulnerabilities.
Discussion:
Oh okay. I guess I thought it was simpler to track a single issue in
just one bug report, but I guess splitting them out may help ... ? I
hope it does.
---
The current version of the .src.rpm is
mailman-2.1.5-32.fc3.src.rpm
at
---
Can someone check the src.rpm I made with the lateest mailman from legacy and
the patches from RHEL?
http://bugs.unl.edu.ar/~martin/mailman-2.1.5-33.fc3.legacy
Bugzilla
CVE-2006-4624 mailman 2.1.9 needed (CVE-2006-3636 CVE-2006-2941)
bugzilla·2006-10-07·CVSS 5.0
CVE-2006-4624 [MEDIUM] CVE-2006-4624 mailman 2.1.9 needed (CVE-2006-3636 CVE-2006-2941)
CVE-2006-4624 mailman 2.1.9 needed (CVE-2006-3636 CVE-2006-2941)
+++ This bug was initially created as a clone of Bug #206607 +++
FC6 needs mailman 2.1.9 to correct CVE-2006-4624, CVE-2006-3636, CVE-2006-2941
This bug is for FC3 and FC4. Upgrading to mailman 2.1.9 will correct these
vulnerabilities.
Discussion:
In a fedora-legacy-list message (),
Martin Marques submitted mailman-2.1.8-1.FC4.1.legacy.src.rpm:
http://bugs.unl.edu.ar/~martin/mailman-2.1.8-1.FC4.1.legacy.src.rpm
This will need to be reviewed and packages built for updates-testing.
Work also needs to be done in the FC3 version of this bug, Bug #211676.
---
Fedora Core 4 is now completely unmaintained. These bugs can't be fixed in that
version. If the issue still persists in current Fedora Core, please reopen.
Thank yo
Bugzilla
CVE-2006-4624 mailman 2.1.9 needed (CVE-2006-3636 CVE-2006-2941)
bugzilla·2006-09-15·CVSS 5.0
CVE-2006-4624 [MEDIUM] CVE-2006-4624 mailman 2.1.9 needed (CVE-2006-3636 CVE-2006-2941)
CVE-2006-4624 mailman 2.1.9 needed (CVE-2006-3636 CVE-2006-2941)
FC6 needs mailman 2.1.9 to correct CVE-2006-4624, CVE-2006-3636, CVE-2006-2941
Bugzilla
CVE-2006-4624 mailman logfile CRLF injection
bugzilla·2006-09-07·CVSS 5.0
CVE-2006-4624 [MEDIUM] CVE-2006-4624 mailman logfile CRLF injection
CVE-2006-4624 mailman logfile CRLF injection
mailman logfile CRLF injection
Text taken from MITRE:
CRLF injection vulnerability in Utils.py in Mailman before 2.1.9rc1
allows remote attackers to spoof messages in the error log and
possibly trick the administrator into visiting malicious URLs via a
carriage return/line feed sequences in the URI.
The fix for this issue is here:
http://svn.sourceforge.net/viewvc/mailman/?revision=7918&view=rev
Discussion:
Bug #206607 also lists these two additional CVE's: CVE-2006-3636 CVE-2006-2941.
The solution for FC6Test3 was to upgrade to mailman 2.1.9. Any plans to do
likewise for this bug as well?
Those issues bring the current FC5 mailman to a security impact of "moderate,"
I believe?
---
The version 2.1.9 is available in FC-5 updates.
Bugzilla
CVE-2006-4624 mailman logfile CRLF injection
bugzilla·2006-09-07·CVSS 2.6
CVE-2006-4624 [LOW] CVE-2006-4624 mailman logfile CRLF injection
CVE-2006-4624 mailman logfile CRLF injection
mailman logfile CRLF injection
Text taken from MITRE:
CRLF injection vulnerability in Utils.py in Mailman before 2.1.9rc1
allows remote attackers to spoof messages in the error log and
possibly trick the administrator into visiting malicious URLs via a
carriage return/line feed sequences in the URI.
The fix for this issue is here:
http://svn.sourceforge.net/viewvc/mailman/?revision=7918&view=rev
This issue also affects RHEL3
This issue also affects RHEL2.1
Discussion:
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update rele
CWE
Improper Output Neutralization for Logs
mitre_cwe
CWE-117 Improper Output Neutralization for Logs
CWE-117: Improper Output Neutralization for Logs
The product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file.
Background: Applications typically use log files to store a history of events or transactions for later review, statistics gathering, or debugging. Depending on the nature of the application, the task of reviewing log files may be performed manually on an as-needed basis or automated with a tool that automatically culls logs for important events or trending information.
Modes of Introduction:
Phase: Implementation
Note: REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Common Consequences:
Scope: Integrity, Confidentiality,
CWE
Improper Neutralization of CRLF Sequences ('CRLF Injection')
mitre_cwe
CWE-93 Improper Neutralization of CRLF Sequences ('CRLF Injection')
CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection')
The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.
Modes of Introduction:
Phase: Implementation
Note: REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Common Consequences:
Scope: Integrity. Impact: Modify Application Data.
Detection Methods:
Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flo
http://mail.python.org/pipermail/mailman-announce/2006-September/000087.htmlhttp://moritz-naumann.com/adv/0013/mailmanmulti/0013.txthttp://secunia.com/advisories/21732http://secunia.com/advisories/22011http://secunia.com/advisories/22020http://secunia.com/advisories/22227http://secunia.com/advisories/22639http://secunia.com/advisories/27669http://security.gentoo.org/glsa/glsa-200609-12.xmlhttp://sourceforge.net/project/shownotes.php?group_id=103&release_id=444295http://svn.sourceforge.net/viewvc/mailman/trunk/mailman/Mailman/Utils.py?r1=7859&r2=7923http://www.debian.org/security/2006/dsa-1188http://www.mandriva.com/security/advisories?name=MDKSA-2006:165http://www.novell.com/linux/security/advisories/2006_25_sr.htmlhttp://www.redhat.com/support/errata/RHSA-2007-0779.htmlhttp://www.securityfocus.com/archive/1/445992/100/0/threadedhttp://www.securityfocus.com/bid/19831http://www.securityfocus.com/bid/20021http://www.vupen.com/english/advisories/2006/3446https://exchange.xforce.ibmcloud.com/vulnerabilities/28734https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9756http://mail.python.org/pipermail/mailman-announce/2006-September/000087.htmlhttp://moritz-naumann.com/adv/0013/mailmanmulti/0013.txthttp://secunia.com/advisories/21732http://secunia.com/advisories/22011http://secunia.com/advisories/22020http://secunia.com/advisories/22227http://secunia.com/advisories/22639http://secunia.com/advisories/27669http://security.gentoo.org/glsa/glsa-200609-12.xmlhttp://sourceforge.net/project/shownotes.php?group_id=103&release_id=444295http://svn.sourceforge.net/viewvc/mailman/trunk/mailman/Mailman/Utils.py?r1=7859&r2=7923http://www.debian.org/security/2006/dsa-1188http://www.mandriva.com/security/advisories?name=MDKSA-2006:165http://www.novell.com/linux/security/advisories/2006_25_sr.htmlhttp://www.redhat.com/support/errata/RHSA-2007-0779.htmlhttp://www.securityfocus.com/archive/1/445992/100/0/threadedhttp://www.securityfocus.com/bid/19831http://www.securityfocus.com/bid/20021http://www.vupen.com/english/advisories/2006/3446https://exchange.xforce.ibmcloud.com/vulnerabilities/28734https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9756
2006-09-07
Published