/ 
Yancy-1.088
River stage one • 4 direct dependents • 4 total dependents
⭐ Starred 54 GitHub stars
/ t/lib/Local/Test.pm
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.

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.

SYNOPSIS

use Test::More;
use Local::Test qw( test_backend init_backend );

subtest 'test my backend' => \&test_backend, $backend_object,
    schema => { ... },
    $list_objects,
    $set_object,
    $create_object;

DESCRIPTION

This module contains helper routines for testing Yancy.

SEE ALSO

Test::Builder

my ( $url, $backend, %out_items ) = init_backend( $schema, %items );

Initialize a backend for testing with the given items. This routine will check the TEST_YANCY_BACKEND environment variable for connection details, if any. Otherwise, it will create a Yancy::Backend::Memory object for mock testing.

NOTE: This routine will delete all existing data in the given schema!

my $result = test_backend(
    $backend, $schema_name, $schema,
    $list, $create, $set_to,
);

Test that a backend works properly. $backend is a backend object. $schema_name is the schema name to test. $schema is the JSON schema. $list is a list of objects already in the backend. $create is a new object to test creating an object. $set_to is values the newly-create object will be set to, before being deleted.

backend_common( $backend, \&insert_item, $schema );

Runs various tests on the given Yancy::Backend instance. The code is a backend-specific procedure to create items, probably a closure.

my %schema = load_fixtures( 'foreign-key-field', 'auth' );

Load the given test fixtures for the database we're currently testing (loaded from "init_backend" using the TEST_YANCY_BACKEND environment variable). Test fixtures are directories with the given files:

schema.json     - The JSON schema
*.sql           - The SQL schema, named for the backend ("sqlite", "pg", "mysql")

Returns the combined schema ready to be passed-in to a backend or the Yancy plugin.

4 POD Errors

The following errors were encountered while parsing the POD:

Around line 36:

Unknown directive: =sub

Around line 364:

Unknown directive: =sub

Around line 772:

Unknown directive: =sub

Around line 1223:

Unknown directive: =sub