SA-CONTRIB-2015-069 – Taxonomy Accordion – Cross Site Scripting (XSS) – Unsupported

Description

Taxonomy Accordion module creates a block for each taxonomy vocabularies.

The module doesn’t sufficiently sanitize user supplied text in some pages, thereby exposing a Cross Site Scripting vulnerability.

This vulnerability is mitigated by the fact that an attacker must have a user allowed to create/edit taxonomy terms.

CVE identifier(s) issued

  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

  • All versions of Taxonomy Accordion module

Drupal core is not affected. If you do not use the contributed Taxonomy Accordion module, there is nothing you need to do.

Solution

If you use the Taxonomy Accordion module you should uninstall it.

Also see the Taxonomy Accordion project page.

Reported by

Fixed by

Not applicable.

Coordinated by

Contact and More Information

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

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Drupal version: 

SA-CONTRIB-2015-068 – Campaign Monitor – Cross Site Request Forgery (CSRF) – Unsupported

Description

Campaign Monitor module integrates the Campaign Monitor API into Drupal.

The module doesn’t sufficiently protect some URLs against CSRF. A malicious user can cause another user to enable and disable list subscriptions by getting their browser to make a request to a specially-crafted URL.

CVE identifier(s) issued

  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

  • Campaign Monitor 7.x-1.0

Drupal core is not affected. If you do not use the contributed Campaign Monitor module, there is nothing you need to do.

Solution

If you use the Campaign Monitor module for Drupal 7 you should uninstall it.

Also see the Campaign Monitor project page.

Reported by

Fixed by

Not applicable.

Coordinated by

Contact and More Information

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

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Drupal version: 

SA-CONTRIB-2015-067 – Finder – Open Redirect – Unsupported

Description

Finder module allows you to create flexible faceted search forms to find entities such as nodes or users based on the values of fields and database attributes.

The provided function finder_form_goto() is susceptible to a phishing attack. An attacker could formulate a redirect in a way that gets the Drupal site to send the user to an arbitrarily provided URL.

CVE identifier(s) issued

  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

  • All versions of Finder module

Drupal core is not affected. If you do not use the contributed Finder module, there is nothing you need to do.

Solution

If you use the Finder module you should uninstall it.

Also see the Finder project page.

Reported by

Fixed by

Not applicable.

Coordinated by

Contact and More Information

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

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Drupal version: 

SA-CONTRIB-2015-066 – Tracking Code – Cross Site Request Forgery (CSRF) – Unsupported

Description

Tracking Code module allows you to create tracking code snippets and control their visibility.

The module doesn’t sufficiently protect some URLs against CSRF. A malicious user can cause an administrator to disable tracking codes by getting their browser to make a request to a specially-crafted URL.

CVE identifier(s) issued

  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

  • All versions of Tracking Code module

Drupal core is not affected. If you do not use the contributed Tracking Code module, there is nothing you need to do.

Solution

If you use the Tracking Code module you should uninstall it.

Also see the Tracking Code project page.

Reported by

Fixed by

Not applicable.

Coordinated by

Contact and More Information

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

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Drupal version: 

SA-CONTRIB-2015-065 – Registration codes – Multiple vulnerabilities – Unsupported

Description

Registration codes module allows new account registrations only for users who provide a valid registration code.

The module was not properly sanitizing user supplied text in some pages, thereby exposing XSS vulnerabilities.

Additionally, some URLs were not protected against CSRF, a malicious user can cause an administrator to delete rules by getting their browser to make a request to a specially-crafted URL.

The XSS vulnerabilities may be mitigated by the fact that an attacker must have a user allowed to create/edit taxonomy terms or nodes.

CVE identifier(s) issued

  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

  • All versions of Registration codes

Drupal core is not affected. If you do not use the contributed Registration codes module, there is nothing you need to do.

Solution

If you use the Registration codes module you should uninstall it.

Also see the Registration codes project page.

Reported by

Fixed by

Not applicable.

Coordinated by

Contact and More Information

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

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Drupal version: 

SA-CONTRIB-2015-064 – Ubercart Discount Coupons – Cross Site Scripting (XSS)

Description

Ubercart Discount Coupons module provides discount coupons for Ubercart stores.

The module doesn’t sufficiently sanitize user supplied text in some administration pages, thereby exposing a Cross Site Scripting vulnerability.

The vulnerability is mitigated by the fact that an attacker must have a user with permission to create/edit taxonomy terms. Note that for vocabularies with free tagging enabled, this includes any user with permission to add/edit content of a type to which the vocabulary applies.

CVE identifier(s) issued

  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

  • Ubercart Discount Coupons 6.x-1.x versions prior to 6.x-1.8

Drupal core is not affected. If you do not use the contributed Ubercart Discount Coupons module, there is nothing you need to do.

Solution

Install the latest version:

Also see the Ubercart Discount Coupons project page.

Reported by

Fixed by

  • wodenx the module maintainer

Coordinated by

Contact and More Information

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

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Drupal version: 

SA-CONTRIB-2015-063 – Webform – Cross Site Scripting (XSS)

Description

Webform enables you to create surveys, personalized contact forms, contests, and the like.

Cross Site Scripting Related to Webform Submissions

The module doesn’t sufficiently escape user data presented to administrative users in the webform results table. This issue affects the 7.x-4.x branch only.

This vulnerability is mitigated by the fact that an attacker must have a role with permission to submit a webform and the administrative user must subsequently visit the webform’s results table tab.

To mitigate this vulnerability, you can disable the view-based results table and restore the legacy hard-coded results table by adding this line to your settings.php file:

<?php
 $conf
['webform_table'] = TRUE;
?>

Cross Site Scripting Related to Blocks

The module doesn’t sufficiently escape node titles of webforms which administrators may make available as blocks and displayed to any user. This issue affects all 6.x and 7.x branches of the module.

This vulnerability is mitigated by the fact that an attacker must have a role with permission to administer blocks and create or edit webform nodes.

CVE identifier(s) issued

  • A CVE identifier will be requested, and added upon issuance, in accordance
    with Drupal Security Team processes.

Versions affected

  • webform 6.x versions prior to 6.x-3.22.
  • webform 7.x-3.x versions prior to 7.x-3.22.
  • webform 7.x-4.x versions prior to 7.x-4.4.

Drupal core is not affected. If you do not use the contributed Webform module,
there is nothing you need to do.

Solution

Install the latest version:

Also see the Webform project page.

Reported by

Fixed by

Coordinated by

Contact and More Information

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

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Drupal version: 

CSRF in Contact Form DB allows attacker to delete all stored form submissions (WordPress plugin)

Posted by dxw Security on Mar 04

Details
================
Software: Contact Form DB
Version: 2.8.29
Homepage: https://wordpress.org/plugins/contact-form-7-to-database-extension/
Advisory report:
https://security.dxw.com/advisories/csrf-in-contact-form-db-allows-attacker-to-delete-all-stored-form-submissions/
CVE: CVE-2015-1874
CVSS: 4.3 (Medium; AV:N/AC:M/Au:N/C:N/I:P/A:N)

Description
================
CSRF in Contact Form DB allows attacker to delete all stored form…

Firefox 37 to Include New OneCRL Certificate Blocklist

The next version of Mozilla Firefox will include a new certificate revocation list that will speed up and streamline the process of revoking intermediate certificates trusted by the browser. The new feature, known as OneCRL, is meant as a replacement for the old OCSP (online certificate status protocol) system that is used now to check […]

My employer is stalking me online!

Would you know if your employer is stalking you online? Fortunately, I do.

There’s nothing shady going on though. I agreed to be the subject of an experiment conducted by AVG CEO Gary Kovacs for his keynote speech at Mobile World Congress 2015.

In the keynote he highlighted the growing need for consumers to understand the great wealth of their personal data that is available online.

I offered to be the victim of this experiment as I consider myself a fairly private person online. I rarely use Facebook and Instagram and when I do, the accounts are very much set to friends only.

Other than my very public profile and work for AVG, there should not be a huge amount of information on me as I’m very conscious of not sharing too much.

The team set about looking for me and sure enough, old articles from the print era and other public sources gave them a good picture of who I am, where I have lived, how much my house is worth, and a whole lot more.

Much of this data is a matter of public record. For example, my property in the UK is listed on the electoral register and a scan of Companies House shows I have held company directorships.

Once these little snippets are discovered, they can be used to search with more specific terms that meant relevant articles started to appear at the top of search results.

Before long, the team had built out a profile of me including pictures, data, family, assets, arrests (fortunately none for me) and many other personal details that we generally consider private or safe from public view.

So what can you do to help keep your data private and under control?

In today’s world, there is little chance of us avoiding a digital footprint short of disconnecting and living in the woods. But what we can do is better understand what is being shared and how we can control what appears in public.

Here are FIVE simple tips that you can follow to help you ensure your data doesn’t appear where it shouldn’t:

 

Check your privacy settings

Much of the information found online about us as individuals is found on social network. Photos, posts, groups and comments can be a great way to find out more about a person so make sure that your privacy settings are set so that only the activity you want shared is made public.

Set Up a Google Alert

Google Alerts are a great way to stay on top of any sites or news that may mention your name (or any other term). Setting one up is very simple and you can learn how in this video.

Video

How to set up a Google Alert

Pick your usernames carefully

When setting up an online account or email address, carefully consider whether it should include parts of your real name. Having an email address with your full name such as [email protected] makes it much easier for snoopers to build out a profile of your details. The same goes for account names on web services.

If you can, remove old accounts

When we stop using old web accounts, a forum for example, see if there is a way to disable or delete your account. While you may not be using the service any more, the data will remain there almost indefinitely and can be discovered with just a simple search.

Tick the box

When giving out your personal details be sure to understand what the company or organization collecting them may do with them. Where possible tick the box (or uncheck in some instances) to keep your data private and do not allow personal data to be shared with third parties.