CVE-2010-3089: XSS
Multiple cross-site scripting (XSS) vulnerabilities in GNU Mailman before 2.1.14rc1 allow remote authenticated users to inject arbitrary web script or HTML via vectors involving (1) the list information field or (2) the list description field.
Other sources
Multiple security flaws leading to cross-site scripting (XSS) attacks (execute arbitrary HTML or scripting code) were found in mailman.
1. A security flaw was found in the way Mailman mailing list manager sanitized content of mailing list information HTML template, prior rendering it to the user. A remote mailing list owner could use this flaw to conduct cross-site scripting (XSS) attacks (execute arbitrary HTML or scripting code) when the modified "listinfo" html page is viewed by the user.
2. A security flaw was found in the way Mailman mailing list manager sanitized mailing list description by presenting general mailing list information. A remote mailing list owner could use this flaw to conduct cross-site scripting (XSS) attacks (execute arbitrary HTML or scripting code).
References: [1] http://mail.python.org/pipermail/mailman-announce/2010-September/000150.html
Acknowledgements:
Red Hat would like to thank Mark Sapiro for reporting these flaws.
Affected Software
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What types of attacks are possible with CVE-2010-3089?
CVE-2010-3089 allows remote authenticated users to perform cross-site scripting (XSS) attacks by injecting web scripts or HTML.
What versions of GNU Mailman are affected by CVE-2010-3089?
CVE-2010-3089 affects all versions of GNU Mailman prior to 2.1.14rc1.
How do I fix CVE-2010-3089?
To fix CVE-2010-3089, update GNU Mailman to version 2.1.14rc1 or later.
What are the potential impacts of exploiting CVE-2010-3089?
Exploiting CVE-2010-3089 can lead to the execution of malicious scripts in the context of a user's session, compromising user data.
Is there a way to mitigate CVE-2010-3089 without upgrading?
There are no effective mitigations for CVE-2010-3089 other than upgrading to a fixed version.