FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The last vuln.xml file processed by FreshPorts is:

Revision:  371350
Date:      2014-10-22
Time:      08:54:58Z
Committer: matthew

List all Vulnerabilities, by package

List all Vulnerabilities, by date

These are the vulnerabilities relating to the commit you have selected:

VuXML IDDescription
b3531fe1-2b03-11df-b6db-00248c9b4be7drupal -- multiple vulnerabilities

Drupal Team reports:

A user-supplied value is directly output during installation allowing a malicious user to craft a URL and perform a cross-site scripting attack. The exploit can only be conducted on sites not yet installed.

The API function drupal_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. No user submitted data will be sent to that URL.

Locale module and dependent contributed modules do not sanitize the display of language codes, native and English language names properly. While these usually come from a preselected list, arbitrary administrator input is allowed. This vulnerability is mitigated by the fact that the attacker must have a role with the 'administer languages' permission.

Under certain circumstances, a user with an open session that is blocked can maintain his/her session on the Drupal site, despite being blocked.


Discovery 2010-03-03
Entry 2010-03-08
drupal5
lt 5.22

drupal6
lt 6.16

http://drupal.org/node/731710
b3531fe1-2b03-11df-b6db-00248c9b4be7drupal -- multiple vulnerabilities

Drupal Team reports:

A user-supplied value is directly output during installation allowing a malicious user to craft a URL and perform a cross-site scripting attack. The exploit can only be conducted on sites not yet installed.

The API function drupal_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. No user submitted data will be sent to that URL.

Locale module and dependent contributed modules do not sanitize the display of language codes, native and English language names properly. While these usually come from a preselected list, arbitrary administrator input is allowed. This vulnerability is mitigated by the fact that the attacker must have a role with the 'administer languages' permission.

Under certain circumstances, a user with an open session that is blocked can maintain his/her session on the Drupal site, despite being blocked.


Discovery 2010-03-03
Entry 2010-03-08
drupal5
lt 5.22

drupal6
lt 6.16

http://drupal.org/node/731710
751823d4-f189-11de-9344-00248c9b4be7drupal -- multiple cross-site scripting

Drupal Team reports:

The Contact module does not correctly handle certain user input when displaying category information. Users privileged to create contact categories can insert arbitrary HTML and script code into the contact module administration page. Such a cross-site scripting attack may lead to the malicious user gaining administrative access.

The Menu module does not correctly handle certain user input when displaying the menu administration overview. Users privileged to create new menus can insert arbitrary HTML and script code into the menu module administration page. Such a cross-site scripting attack may lead to the malicious user gaining administrative access.


Discovery 2009-12-16
Entry 2009-12-25
Modified 2010-05-02
drupal5
lt 5.21

drupal6
lt 6.15

CVE-2009-4370
http://drupal.org/node/661586
751823d4-f189-11de-9344-00248c9b4be7drupal -- multiple cross-site scripting

Drupal Team reports:

The Contact module does not correctly handle certain user input when displaying category information. Users privileged to create contact categories can insert arbitrary HTML and script code into the contact module administration page. Such a cross-site scripting attack may lead to the malicious user gaining administrative access.

The Menu module does not correctly handle certain user input when displaying the menu administration overview. Users privileged to create new menus can insert arbitrary HTML and script code into the menu module administration page. Such a cross-site scripting attack may lead to the malicious user gaining administrative access.


Discovery 2009-12-16
Entry 2009-12-25
Modified 2010-05-02
drupal5
lt 5.21

drupal6
lt 6.15

CVE-2009-4370
http://drupal.org/node/661586
bad1b090-a7ca-11de-873f-0030843d3802drupal -- multiple vulnerabilities

Drupal Team reports:

The core OpenID module does not correctly implement Form API for the form that allows one to link user accounts with OpenID identifiers. A malicious user is therefore able to use cross site request forgeries to add attacker controlled OpenID identities to existing accounts. These OpenID identities can then be used to gain access to the affected accounts.

The OpenID module is not a compliant implementation of the OpenID Authentication 2.0 specification. An implementation error allows a user to access the account of another user when they share the same OpenID 2.0 provider.

File uploads with certain extensions are not correctly processed by the File API. This may lead to the creation of files that are executable by Apache. The .htaccess that is saved into the files directory by Drupal should normally prevent execution. The files are only executable when the server is configured to ignore the directives in the .htaccess file.

Drupal doesn't regenerate the session ID when an anonymous user follows the one time login link used to confirm email addresses and reset forgotten passwords. This enables a malicious user to fix and reuse the session id of a victim under certain circumstances.


Discovery 2009-09-17
Entry 2009-09-22
drupal5
lt 5.20

drupal6
lt 6.14

http://drupal.org/node/579482
http://secunia.com/advisories/36787/
http://secunia.com/advisories/36786/
http://secunia.com/advisories/36781/
http://secunia.com/advisories/36776/
http://secunia.com/advisories/36785/
bad1b090-a7ca-11de-873f-0030843d3802drupal -- multiple vulnerabilities

Drupal Team reports:

The core OpenID module does not correctly implement Form API for the form that allows one to link user accounts with OpenID identifiers. A malicious user is therefore able to use cross site request forgeries to add attacker controlled OpenID identities to existing accounts. These OpenID identities can then be used to gain access to the affected accounts.

The OpenID module is not a compliant implementation of the OpenID Authentication 2.0 specification. An implementation error allows a user to access the account of another user when they share the same OpenID 2.0 provider.

File uploads with certain extensions are not correctly processed by the File API. This may lead to the creation of files that are executable by Apache. The .htaccess that is saved into the files directory by Drupal should normally prevent execution. The files are only executable when the server is configured to ignore the directives in the .htaccess file.

Drupal doesn't regenerate the session ID when an anonymous user follows the one time login link used to confirm email addresses and reset forgotten passwords. This enables a malicious user to fix and reuse the session id of a victim under certain circumstances.


Discovery 2009-09-17
Entry 2009-09-22
drupal5
lt 5.20

drupal6
lt 6.14

http://drupal.org/node/579482
http://secunia.com/advisories/36787/
http://secunia.com/advisories/36786/
http://secunia.com/advisories/36781/
http://secunia.com/advisories/36776/
http://secunia.com/advisories/36785/