Yancy-1.054

Security Advisories (9)

CVE-2020-11022 (2020-04-29)

In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.

CVE-2020-11023 (2020-04-29)

In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.

CVE-2019-11358 (2019-04-20)

jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.

CVE-2015-9251 (2018-01-18)

jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.

CVE-2011-4969 (2013-03-08)

Cross-site scripting (XSS) vulnerability in jQuery before 1.6.3, when using location.hash to select elements, allows remote attackers to inject arbitrary web script or HTML via a crafted tag.

CVE-2012-6708 (2018-01-18)

jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.

CVE-2020-7656 (2020-05-19)

jquery prior to 1.9.0 allows Cross-site Scripting attacks via the load method. The load method fails to recognize and remove "<script>" HTML tags that contain a whitespace character, i.e: "</script >", which results in the enclosed script logic to be executed.

CVE-2019-5428

Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as _proto_, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.

https://security.snyk.io/vuln/SNYK-JS-JQUERY-174006

CVE-2014-6071 (2018-01-16)

jQuery 1.4.2 allows remote attackers to conduct cross-site scripting (XSS) attacks via vectors related to use of the text method inside after.

Changes for version 1.054 - 2020-04-19

Important!
- The 'yancy.auth.login' route is now named 'yancy.auth.login_form' to match the other login form routes.
Added
- Added disabling of CSRF field in Form plugins. Use this to build a form without a CSRF token inside.
- Added top-level OR matching to `match` utility. Now the `require_user` authorization method can express more options.
- Added `$match: any` to controller list actions. This changes the filter from "AND" to "OR", returning results that match any filter instead of requiring them to match all filters.
Fixed
- Fixed test failure with too old versions of Test::Mojo::Role::Selenium. Thanks @eserte for reporting this!
  - Github #98
- Fixed `yancy.form.form_for` helper being called with `app` causing CSRF failures. Now the Form helper will warn you when called without a request that can build a useful CSRF token. Thanks @pavelsr for reporting this! [Github #95]
- In the controller list actions, '$order_by' can now be a field name to sort by that field ascending. Previously, the 'asc:' or 'desc:' prefix was required.
- Fixed foreign key fields not working when the first item in x-list-columns was using a template. Now, the foreign key field searches all fields in the template and uses the template to display the current value of the field. Thanks @OpossumPetya for reporting this issue! [Github #96]
- Removed extra page loads from the authentication workflow:
  - The login form is now displayed on the unauthorized error page
  - Logging out brings the user back to where they were so, if necessary, they can log in again
- Fixed user being returned to the wrong place after authentication:
  - If the login form was displayed by the login page, the user is returned to the previous page
  - Otherwise, the login form was displayed on the page the user wants, so they are directed back to that page
  - The `return_to` query param can be used to override where a user is returned in either circumstance
Docs
- Made the docs for Yancy::Controller::Yancy and Yancy::Controller::Yancy::MultiTenant easier to read.
- Added undocumented `login_form` helper to auth plugins
- Added examples of how to use Auth plugin routes and helpers. Thanks @pavelsr for reporting this issue! [Github #100]