Monthly Archives: February 2015

Drupal

SA-CONTRIB-2015-043 – Commerce Balanced Payments – Multiple vulnerabilities

Description

Commerce Balanced Payments module integrates Drupal Commerce with the Balanced Payments third-party service.

The module doesn’t sufficiently sanitize user supplied text in the Bank Account Listing Page, thereby exposing a Cross Site Scripting vulnerability.

Also, some URLs were not protected against CSRF. A malicious user can cause another user to delete their configured bank accounts 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 Commerce Balanced Payments.

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

Solution

If you use the Commerce Balanced Payments module you should uninstall it.

Also see the Commerce Balanced Payments 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: 
Drupal 7.x
Drupal

SA-CONTRIB-2015-042 – Node basket – Multiple vulnerabilities – Unsupported

Description

Node basket module enables you to pick up nodes in a basket.

The module doesn’t sufficiently sanitize user supplied text in some pages, thereby exposing a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a user with permission to create/edit nodes.

Also, the module has CSRF vulnerabilities. A malicious user can cause another user to add/remove nodes of the basket by getting his browser to make a request to a specially-crafted URL.

Also, the module has an Open Redirect vulnerability.

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 Node basket module.

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

Solution

If you use the Node basket module you should uninstall it.

Also see the Node basket 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: 
Drupal 6.x
Drupal

SA-CONTRIB-2015-041 – Feature Set – Cross Site Request Forgery (CSRF) – Unsupported

Description

Feature Set module enables you to enable or disable sets of features or modules.

The module doesn’t sufficiently protect some URLs against CSRF. A malicious user can cause an administrator to enable and disable modules by getting the administrator’s 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 Feature Set module.

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

Solution

If you use the Feature Set module you should uninstall it.

Also see the Feature Set 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: 
Drupal 7.x
Drupal

SA-CONTRIB-2015-040 – Webform prepopulate block – Cross Site Scripting (XSS)

Description

Webform prepopulate block module enables you to set a webform component to display in a separated block.

The module doesn’t sufficiently sanitize user supplied text when displaying the block, thereby exposing a Cross Site Scripting vulnerability.

This vulnerability is mitigated by the fact that an attacker must have a role with permission to create or edit 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 prepopulate block 7.x-3.0

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

Solution

Install the latest version:

Also see the Webform prepopulate block 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: 
Drupal 7.x
Drupal

SA-CONTRIB-2015-039 – Views – Multiple vulnerabilities

Description

The Views module provides a flexible method for Drupal site designers to control how lists and tables of content, users, taxonomy terms and other data are presented.

Open redirect vulnerability

The module does not sanitize user provided URLs when processing the page to break the lock on Views being edited, thereby exposing an open redirect attack vector.

This vulnerability is mitigated by the fact that the Views UI submodule must be enabled.

Access bypass vulnerability

The module does not protect the default Views configurations that ship with the module sufficiently, thereby exposing possibly protected information to unprivileged users.

This vulnerability is mitigated by the fact that it only affects sites that have not granted the common “access content” or “access comments” permission to untrusted users. Furthermore, these default views configurations are disabled by default and must be enabled by an administrator.

CVE identifier(s) issued

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

Versions affected

  • Views 6.x-2.x versions prior to 6.x-2.18.
  • Views 6.x-3.x versions prior to 6.x-3.2.
  • Views 7.x-3.x versions prior to 7.x-3.10.

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

Solution

Install the latest version:

Also see the Views 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: 
Drupal 6.x
Drupal 7.x
Full Disclosure

T-Mobile Internet Manager – DLL Hijacking (mfc71enu.dll)

Posted by Vulnerability Lab on Feb 11

Document Title:
===============
T-Mobile Internet Manager – DLL Hijacking (mfc71enu.dll)

References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=1427

Release Date:
=============
2015-01-29

Vulnerability Laboratory ID (VL-ID):
====================================
1427

Common Vulnerability Scoring System:
====================================
5.6

Product & Service Introduction:…

Panda Security

Cyber Resolutions You’Ve Already Broken

Cyber Resolutions you already broken

Cyber resolutions you’ve already broken

Resolution. I will not reuse passwords

Having different passwords for every website you use increases your safety. A password is only as dependable as the least secure site that has it. You might be attached to  ‘loverboy82’, but time to think of something more original.
Resolution. I will not use passwords a human could guess

It’s the age of social media, and we share a lot more than we think. If your password is a loved one’s name (even with threes instead of ‘e’s), the only thing stopping a hacker is a quick search on your Facebook page – or that of your partner, grandchildren, bowling partner…
Resolution. I will not use passwords a computer could guess

Computers understand word structure and are capable of guessing around one thousand variations a second, so using four random words without spaces, e.g. ‘houseboatchickencannon’, is far more effective, and memorable, than using a one-word password. Thinkofsomethingnowquick.

Resolution. I will not use passwords a monkey could guess

We’re calling time on ‘password’, ‘12345’ and ‘let me in’. The only difference between these passwords and none at all is that these come with the satisfaction of making a hacker waste two minutes of his time.
Resolution. I will not put off updating my anti-virus protection

Think of antivirus as your weapon against online fraud, viruses and worse. “Yeah!” shouts your digital anti-virus warrior. “I’m ready to protect your online safety, as soon as you give me a sword! Um… hello? Anyone?”
Resolution. I will install anti-virus protection on every device that needs it

Sure you already protected the main computer, but is that the only device in the house that you use to go online? Mobile devices and laptops have just as much access to your private information, and they need just as much protection.

Resolution. I will install a parental control on my anti-virus software

Sometimes it seems like kids know more than adults about getting around online, but they certainly don’t know more about staying safe. Parental control gives you the power to keep them that way, monitoring and controlling what they’re exposed to online.

Make your resolutions stay safe.

If you want to share this infographic, here you have the code:

The post Cyber Resolutions You’Ve Already Broken appeared first on MediaCenter Panda Security.

Full Disclosure

Pandora FMS v5.1 SP1 – SQL Injection Web Vulnerability

Posted by Vulnerability Lab on Feb 11

Document Title:
===============
Pandora FMS v5.1 SP1 – SQL Injection Web Vulnerability

References (Source):
====================
http://vulnerability-lab.com/get_content.php?id=1355

Release Date:
=============
2015-02-09

Vulnerability Laboratory ID (VL-ID):
====================================
1355

Common Vulnerability Scoring System:
====================================
6.3

Product & Service Introduction:
===============================…

Full Disclosure

BlinkSale Bug Bounty #1 – Encode & Validation Vulnerability

Posted by Vulnerability Lab on Feb 11

Document Title:
===============
BlinkSale Bug Bounty #1 – Encode & Validation Vulnerability

References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=1416

Release Date:
=============
2015-02-06

Vulnerability Laboratory ID (VL-ID):
====================================
1416

Common Vulnerability Scoring System:
====================================
3.6

Product & Service Introduction:…

Full Disclosure

Facebook Bug Bounty #23 – Session ID & CSRF Vulnerability

Posted by Vulnerability Lab on Feb 11

Document Title:
===============
Facebook Bug Bounty #23 – Session ID & CSRF Vulnerability

References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=1432

Facebook Security ID: 10202805822321483

Video: https://www.youtube.com/watch?v=SAr2AGLrBkQ

Vulnerability Magazine:
http://magazine.vulnerability-db.com/?q=articles/2015/02/03/facebook-security-12500-bug-bounty-reward-security-researcher

Release Date:…