The documents application in ownCloud Server 6.x before 6.0.6 and 7.x before 7.0.3 allows remote authenticated users to obtain all valid session IDs via an unspecified API method.
Monthly Archives: February 2015
CVE-2014-9562
Cross-site scripting (XSS) vulnerability in display_dialog.php in M2 OptimalSite 0.1 and 2.4 allows remote attackers to inject arbitrary web script or HTML via the image parameter.
CVE-2015-1481
Ansible Tower (aka Ansible UI) before 2.0.5 allows remote organization administrators to gain privileges by creating a superuser account.
CVE-2015-1482
Ansible Tower (aka Ansible UI) before 2.0.5 allows remote attackers to bypass authentication and obtain sensitive information via a websocket connection to socket.io/1/.
SA-CONTRIB-2015-038 – Facebook Album Fetcher – Cross Site Scripting (XSS) – Unsupported
- Advisory ID: DRUPAL-SA-CONTRIB-2015-038
- Project: Facebook Album Fetcher (third-party module)
- Version: 7.x
- Date: 2015-February-04
- Security risk: 12/25 ( Moderately Critical) AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:Default
- Vulnerability: Cross Site Scripting
Description
Facebook Album Fetcher module allows you to fetch Facebook albums from a Facebook account.
The module incorrectly prints fields without proper sanitization thereby exposing a Cross Site Scripting vulnerability.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission “access administration pages”.
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 Facebook Album Fetcher.
Drupal core is not affected. If you do not use the contributed Facebook Album Fetcher module,
there is nothing you need to do.
Solution
If you use the Facebook Album Fetcher module you should uninstall it.
Also see the Facebook Album Fetcher project page.
Reported by
- Pere Orga of the Drupal Security Team
Fixed by
Not applicable.
Coordinated by
- Pere Orga of the Drupal Security Team
- Rick Manelius of the Drupal Security Team
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
SA-CONTRIB-2015-037 – Path Breadcrumbs – Access Bypass
- Advisory ID: DRUPAL-SA-CONTRIB-2015-037
- Project: Path Breadcrumbs (third-party module)
- Version: 7.x
- Date: 2015-February-04
- Security risk: 12/25 ( Moderately Critical) AC:Basic/A:None/CI:Some/II:None/E:Theoretical/TD:Default
- Vulnerability: Access bypass
Description
This module enables you to configure breadcrumbs for any Drupal page.
The module doesn’t check node access on 403 Not Found pages. As a result, unpublished content data can be shown to unprivileged user.
This vulnerability is mitigated by the fact that it is possible to configure proper access control in Path Breadcrumbs items with “Selection Rules” from the UI.
CVE identifier(s) issued
- A CVE identifier will be requested, and added upon issuance, in accordance
with Drupal Security Team processes.
Versions affected
- Path Breadcrumbs 7.x-3.x versions prior to 7.x-3.2
Drupal core is not affected. If you do not use the contributed Path Breadcrumbs module,
there is nothing you need to do.
Solution
Install the latest version:
- If you use the Path Breadcrumbs module for Drupal 7.x, upgrade to Path Breadcrumbs 7.x-3.2
Also see the Path Breadcrumbs project page.
Reported by
Fixed by
- Kate Marshalkina and Evgeniy Maslovskiy, the module maintainers
Coordinated by
- Greg Knaddison of the Drupal Security Team
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
The utterly crazy story of the death threat hacker (involves a cat)
A cat leads to a notorious death threat hacker finally being caught and jailed in Japan.
The post The utterly crazy story of the death threat hacker (involves a cat) appeared first on We Live Security.
SA-CONTRIB-2015-036 – Public Download Count – Cross Site Scripting (XSS) – Unsupported
- Advisory ID: DRUPAL-SA-CONTRIB-2015-036
- Project: Public Download Count (third-party module)
- Version: 7.x
- Date: 2015-February-04
- Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All
- Vulnerability: Cross Site Scripting
Description
Public Download Count module keeps track of file download counts.
The module doesn’t sufficiently sanitize user supplied text in the Download counts report page 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
- All versions of Public Download Count module.
Drupal core is not affected. If you do not use the contributed Public Download Count module,
there is nothing you need to do.
Solution
If you use the Public Download Count module you should uninstall it.
Also see the Public Download Count project page.
Reported by
- Pere Orga of the Drupal Security Team
Fixed by
Not applicable.
Coordinated by
- Pere Orga of the Drupal Security Team
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
SA-CONTRIB-2015-035 – Ajax Timeline – Cross Site Scripting (XSS)
- Advisory ID: DRUPAL-SA-CONTRIB-2015-035
- Project: Ajax Timeline (third-party module)
- Version: 7.x
- Date: 2015-February-04
- Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All
- Vulnerability: Cross Site Scripting
Description
Ajax Timeline module enables you to display a vertical timeline of nodes based off a date field or created date of the configured nodes.
The module doesn’t sufficiently escape node titles when displaying the timeline, allowing a malicious user to inject code.
This vulnerability is mitigated by the fact that an attacker must have a role with permission to create or edit nodes of the type configured for the timeline.
CVE identifier(s) issued
- A CVE identifier will be requested, and added upon issuance, in accordance
with Drupal Security Team processes.
Versions affected
- Ajax Timeline 7.x-1.x versions prior to 7.x-1.1.
Drupal core is not affected. If you do not use the contributed Ajax Timeline module,
there is nothing you need to do.
Solution
Install the latest version:
- If you use the Ajax Timeline module for Drupal 7.x, upgrade to Ajax Timeline 7.x-1.1.
Also see the Ajax Timeline project page.
Reported by
- Pere Orga of the Drupal Security Team
Fixed by
- Bryan Sharpe the module maintainer
Coordinated by
- Pere Orga of the Drupal Security Team
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
SA-CONTRIB-2015-034 – Commerce WeDeal – Open Redirect
- Advisory ID: DRUPAL-SA-CONTRIB-2015-034
- Project: Commerce WeDeal (third-party module)
- Version: 7.x
- Date: 2015-February-04
- Security risk: 10/25 ( Moderately Critical) AC:Basic/A:None/CI:None/II:None/E:Theoretical/TD:All
- Vulnerability: Open Redirect
Description
Commerce WeDeal module enables you to do Commerce payments through the payment provider WeDeal.
The module doesn’t sufficiently check a query parameter used for page redirection, thereby leading to 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
- Commerce WeDeal 7.x-1.x versions prior to 7.x-1.3.
Drupal core is not affected. If you do not use the contributed Commerce WeDeal module,
there is nothing you need to do.
Solution
Install the latest version:
- If you use the Commerce WeDeal module for Drupal 7.x, upgrade to Commerce WeDeal 7.x-1.3
Also see the Commerce WeDeal project page.
Reported by
- Pere Orga of the Drupal Security Team
Fixed by
- Jeroen Bobbeldijk the module maintainer
Coordinated by
- Pere Orga of the Drupal Security Team
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