/ 
Yancy-1.088
River stage one • 4 direct dependents • 4 total dependents
⭐ Starred 54 GitHub stars
/ Yancy::Util
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.

NAME

Yancy::Util - Utilities for Yancy

VERSION

version 1.088

SYNOPSIS

use Yancy::Util qw( load_backend );
my $be = load_backend( 'memory://localhost', $schema );

use Yancy::Util qw( curry );
my $helper = curry( \&_helper_sub, @args );

use Yancy::Util qw( currym );
my $sub = currym( $object, 'method_name', @args );

use Yancy::Util qw( match );
if ( match( $where, $item ) ) {
    say 'Matched!';
}

use Yancy::Util qw( fill_brackets );
my $value = fill_brackets( $template, $item );

DESCRIPTION

This module contains utility functions for Yancy.

SUBROUTINES

load_backend

my $backend = load_backend( $backend_url, $schema );
my $backend = load_backend( { $backend_name => $arg }, $schema );
my $backend = load_backend( $db_object, $schema );

Get a Yancy backend from the given backend URL, or from a hash reference with a backend name and optional argument. The $schema hash is the configured JSON schema for this backend.

A backend URL should begin with a name followed by a colon. The first letter of the name will be capitalized, and used to build a class name in the Yancy::Backend namespace.

The $backend_name should be the name of a module in the Yancy::Backend namespace. The $arg is handled by the backend module. Read your backend module's documentation for details.

The $db_object can be one of: Mojo::Pg, Mojo::mysql, Mojo::SQLite, or a subclass of DBIx::Class::Schema. The appropriate backend object will be created.

See "Database Backend" in Yancy::Guides::Schema for information about backend URLs and Yancy::Backend for more information about backend objects.

curry

my $curried_sub = curry( $sub, @args );

Return a new subref that, when called, will call the passed-in subref with the passed-in @args first.

For example:

my $add = sub {
    my ( $lop, $rop ) = @_;
    return $lop + $rop;
};
my $add_four = curry( $add, 4 );
say $add_four->( 1 ); # 5
say $add_four->( 2 ); # 6
say $add_four->( 3 ); # 7

This is more-accurately called partial application, but curry is shorter.

currym

my $curried_sub = currym( $obj, $method, @args );

Return a subref that, when called, will call given $method on the given $obj with any passed-in @args first.

See "curry" for an example.

copy_inline_refs

my $subschema = copy_inline_refs( $schema, '/user' );

Given:

a "source" JSON schema (will not be mutated)
a JSON Pointer into the source schema, from which to be copied

will return another, copied standalone JSON schema, with any $ref either copied in, or if previously encountered, with a $ref to the new location.

match

my $bool = match( $where, $item );

Test if the given $item matches the given SQL::Abstract $where data structure. See "WHERE CLAUSES" in SQL::Abstract for the full syntax.

Not all of SQL::Abstract's syntax is supported yet, so patches are welcome.

order_by

my $ordered_array = order_by( $order_by, $unordered_array );

Order the given arrayref by the given SQL::Abstract order-by clause.

fill_brackets

my $string = fill_brackets( $template, $item );

This routine will fill in the given template string with the values from the given $item hashref. The template contains field names within curly braces. Values in the $item hashref will be escaped with "xml_escape" in Mojo::Util.

my $item = {
    name => 'Doug Bell',
    email => 'doug@example.com',
    quote => 'I <3 Perl',
};

# Doug Bell <doug@example.com>
fill_brackets( '{name} <{email}>', $item );

# I &lt;3 Perl
fill_brackets( '{quote}', $item );

is_type

my $bool = is_type( $schema->{properties}{myprop}{type}, 'boolean' );

Returns true if the given JSON schema type value (which can be a string or an array of strings) contains the given value, allowing the given type for the property.

# true
is_type( 'boolean', 'boolean' );
is_type( [qw( boolean null )], 'boolean' );
# false
is_type( 'string', 'boolean' );
is_type( [qw( string null )], 'boolean' );

is_format

my $bool = is_format( $schema->{properties}{myprop}{format}, 'date-time' );

Returns true if the given JSON schema format value (a string) is the given value.

# true
is_format( 'date-time', 'date-time' );
# false
is_format( 'email', 'date-time' );

derp

derp "This feature is deprecated in file '%s'", $file;

Print out a deprecation message as a warning. A message will only be printed once for each set of arguments from each caller.

json_validator

my $json_validator = json_validator( $schema );

Build a JSON::Validator object for the given schema, adding all the necessary attributes.

SEE ALSO

Yancy

AUTHOR

Doug Bell <preaction@cpan.org>

COPYRIGHT AND LICENSE

This software is copyright (c) 2021 by Doug Bell.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.