SA-CONTRIB-2014-088 - Mollom - Cross-site scripting (XSS)

[paul]

View online: ​https://www.drupal.org/node/2340029

• Advisory ID: DRUPAL-SA-CONTRIB-2014-088
• Project: Mollom [1] (third-party module)
• Version: 6.x, 7.x
• Date: 2014-September-17
• Security risk: 11/25 ( Moderately Critical)

AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:Uncommon [2]

• Vulnerability: Cross Site Scripting

---

---

Mollom is an "intelligent" content moderation web service which determines if
a post is potentially spam; not only based on the posted content, but also on
the past activity and reputation of the poster across multiple sites.

Mollom offers a feature to report submitted content as inappropriate which
allows end users to indicate that a piece of site content is objectionable or
out of place. When reporting content, the content title is not sufficiently
sanitized to prevent cross-site scripting (XSS) attacks.

This vulnerability is mitigated by the fact that an attacker must have a role
with the permission to create content and the content type must be enabled
for "Flag as Inappropriate" within the Mollom advanced configuration settings
(which is not the default setting).

---

---

• /A CVE identifier [3] will be requested, and added upon issuance, in

accordance
with Drupal Security Team processes./

---

---

• Mollom 6.x-2.x versions from 6.x-2.7 to 6.x-2.10
• Mollom 7.x-2.x versions from 7.x-2.9 to 7.x-2.10

Drupal core is not affected. If you do not use the contributed Mollom [4]
module,
there is nothing you need to do.

---

---

Install the latest version:

• If you use the Mollom module for Drupal 6.x, upgrade to Mollom 6.x-2.11

[5]

• If you use the Mollom module for Drupal 7.x, upgrade to Mollom 7.x-2.11

[6]

Also see the Mollom [7] project page.

---

---

• Matt Vance [8]

---

---

• Lisa Backer [9] the module maintainer
• Matt Vance [10]

---

---

• Greg Knaddison [11] of the Drupal Security Team

---

---

The Drupal security team can be reached at security at drupal.org or via the
contact form at ​https://www.drupal.org/contact [12].

Learn more about the Drupal Security team and their policies [13],
writing secure code for Drupal [14], and
securing your site [15].

[1] ​https://www.drupal.org/project/mollom
[2] ​https://www.drupal.org/security-team/risk-levels
[3] ​http://cve.mitre.org/
[4] ​https://www.drupal.org/project/mollom
[5] ​https://www.drupal.org/node/2338787
[6] ​https://www.drupal.org/node/2338789
[7] ​https://www.drupal.org/project/mollom
[8] ​https://www.drupal.org/user/88338
[9] ​https://www.drupal.org/user/1951462
[10] ​https://www.drupal.org/user/88338
[11] ​https://www.drupal.org/user/36762
[12] ​https://www.drupal.org/contact
[13] ​https://www.drupal.org/security-team
[14] ​https://www.drupal.org/writing-secure-code
[15] ​https://www.drupal.org/security/secure-configuration

[paul]

Updating now ..

[paul]

Done.

Manually updated the module on production. Profile did not need updating.

[ed]

changed to maintenance milestone for monthly tally