Date: Sun, 27 Nov 2016 03:25:52 +0000 (UTC) From: Jason Unovitch <junovitch@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r427190 - head/security/vuxml Message-ID: <201611270325.uAR3Pqar057321@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: junovitch Date: Sun Nov 27 03:25:52 2016 New Revision: 427190 URL: https://svnweb.freebsd.org/changeset/ports/427190 Log: Remove trailing period in version and re-wrap Drupal entry at <=80 lines PR: 214813 Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Sun Nov 27 03:07:49 2016 (r427189) +++ head/security/vuxml/vuln.xml Sun Nov 27 03:25:52 2016 (r427190) @@ -67,22 +67,48 @@ Notes: </package> <package> <name>drupal8</name> - <range><ge>8.0.0</ge><lt>8.2.3.</lt></range> + <range><ge>8.0.0</ge><lt>8.2.3</lt></range> </package> </affects> <description> <body xmlns="http://www.w3.org/1999/xhtml">; <p>The Drupal development team reports:</p> <blockquote cite="https://www.drupal.org/SA-CORE-2016-005">; - <h3>Inconsistent name for term access query (Less critical - Drupal 7 and Drupal 8)</h3> - <p>Drupal provides a mechanism to alter database SELECT queries before they are executed. Contributed and custom modules may use this mechanism to restrict access to certain entities by implementing hook_query_alter() or hook_query_TAG_alter() in order to add additional conditions. Queries can be distinguished by means of query tags. As the documentation on EntityFieldQuery::addTag() suggests, access-tags on entity queries normally follow the form ENTITY_TYPE_access (e.g. node_access). However, the taxonomy module's access query tag predated this system and used term_access as the query tag instead of taxonomy_term_access.</p> - <p>As a result, before this security release modules wishing to restrict access to taxonomy terms may have implemented an unsupported tag, or needed to look for both tags (term_access and taxonomy_term_access) in order to be compatible with queries generated both by Drupal core as well as those generated by contributed modules like Entity Reference. Otherwise information on taxonomy terms might have been disclosed to unprivileged users.</p> - <h3>Incorrect cache context on password reset page (Less critical - Drupal 8)</h3> - <p>The user password reset form does not specify a proper cache context, which can lead to cache poisoning and unwanted content on the page.</p> - <h3>Confirmation forms allow external URLs to be injected (Moderately critical - Drupal 7)</h3> - <p>Under certain circumstances, malicious users could construct a URL to a confirmation form that would trick users into being redirected to a 3rd party website after interacting with the form, thereby exposing the users to potential social engineering attacks.</p> - <h3>Denial of service via transliterate mechanism (Moderately critical - Drupal 8)</h3> - <p>A specially crafted URL can cause a denial of service via the transliterate mechanism.</p> + <h3>Inconsistent name for term access query (Less critical - Drupal + 7 and Drupal 8)</h3> + <p>Drupal provides a mechanism to alter database SELECT queries before + they are executed. Contributed and custom modules may use this + mechanism to restrict access to certain entities by implementing + hook_query_alter() or hook_query_TAG_alter() in order to add + additional conditions. Queries can be distinguished by means of + query tags. As the documentation on EntityFieldQuery::addTag() + suggests, access-tags on entity queries normally follow the form + ENTITY_TYPE_access (e.g. node_access). However, the taxonomy + module's access query tag predated this system and used term_access + as the query tag instead of taxonomy_term_access.</p> + <p>As a result, before this security release modules wishing to + restrict access to taxonomy terms may have implemented an + unsupported tag, or needed to look for both tags (term_access and + taxonomy_term_access) in order to be compatible with queries + generated both by Drupal core as well as those generated by + contributed modules like Entity Reference. Otherwise information + on taxonomy terms might have been disclosed to unprivileged users. + </p> + <h3>Incorrect cache context on password reset page (Less critical - + Drupal 8)</h3> + <p>The user password reset form does not specify a proper cache + context, which can lead to cache poisoning and unwanted content on + the page.</p> + <h3>Confirmation forms allow external URLs to be injected (Moderately + critical - Drupal 7)</h3> + <p>Under certain circumstances, malicious users could construct a URL + to a confirmation form that would trick users into being redirected + to a 3rd party website after interacting with the form, thereby + exposing the users to potential social engineering attacks.</p> + <h3>Denial of service via transliterate mechanism (Moderately critical + - Drupal 8)</h3> + <p>A specially crafted URL can cause a denial of service via the + transliterate mechanism.</p> </blockquote> </body> </description> @@ -95,6 +121,7 @@ Notes: <dates> <discovery>2016-11-16</discovery> <entry>2016-11-25</entry> + <modified>2016-11-27</modified> </dates> </vuln>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201611270325.uAR3Pqar057321>