/ 
UR-0.47
⭐ Starred 3
/ ur
Security Advisories (12)
CVE-2018-14041 (2018-07-13)

In Bootstrap before 4.1.2, XSS is possible in the data-target property of scrollspy.

CVE-2018-14042 (2018-07-13)

In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.

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.

CVE-2018-14040 (2018-07-13)

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.

NAME

ur test run - Run the test suite against the source tree.

VERSION

This document describes ur test run version 0.29.

SYNOPSIS

ur test run [--color] [--junit] [--list] [--lsf] [--recurse] [--callcount] [--cover=?] [--cover-cvs-changes] [--cover-svk-changes] [--cover-svn-changes] [--coverage] [--inc=?[,?]] [--jobs=?] [--long] [--lsf-params=?] [--noisy] [--perl-opts=?] [--run-as-lsf-helper=?] [--script-opts=?] [--time=?] [BARE-ARGS]

cd MyNamespace ur test run --recurse # run all tests in the namespace ur test run # runs all tests in the t/ directory under pwd ur test run t/mytest1.t My/Class.t # run specific tests ur test run -v -t --cover-svk-changes # run tests to cover latest svk updates ur test run -I ../some/path/ # Adds ../some/path to perl's @INC through -I ur test run --junit # writes test output in junit's xml format (consumable by Hudson integration system)

REQUIRED ARGUMENTS

color Boolean

Use TAP::Harness::Color to generate color output

Default value 'false' (--nocolor) if not specified

nocolor Boolean

Make color 'false'

junit Boolean

Run all tests with junit style XML output. (requires TAP::Formatter::JUnit)

nojunit Boolean

Make junit 'false'

list Boolean

List the tests, but do not actually run them.

nolist Boolean

Make list 'false'

lsf Boolean

If true, tests will be submitted as jobs via bsub

nolsf Boolean

Make lsf 'false'

recurse Boolean

Run all .t files in the current directory, and in recursive subdirectories.

norecurse Boolean

Make recurse 'false'

OPTIONAL ARGUMENTS

callcount Boolean

Count the number of calls to each subroutine/method

nocallcount Boolean

Make callcount 'false'

cover List

Cover only this(these) modules

cover-cvs-changes Boolean

Cover modules modified in cvs status

nocover-cvs-changes Boolean

Make cover-cvs-changes 'false'

cover-svk-changes Boolean

Cover modules modified in svk status

nocover-svk-changes Boolean

Make cover-svk-changes 'false'

cover-svn-changes Boolean

Cover modules modified in svn status

nocover-svn-changes Boolean

Make cover-svn-changes 'false'

coverage Boolean

Invoke Devel::Cover

nocoverage Boolean

Make coverage 'false'

inc String

Additional paths for @INC, alias for -I

jobs Number

How many tests to run in parallel

Default value '1' if not specified

long Boolean

Run tests including those flagged as long

nolong Boolean

Make long 'false'

lsf-params String

Params passed to bsub while submitting jobs to lsf

Default value '-q short -R select[type==LINUX64]' if not specified

noisy Boolean

doesn't redirect stdout

nonoisy Boolean

Make noisy 'false'

perl-opts String

Override options to the Perl interpreter when running the tests (-d:Profile, etc.)

Default value '' if not specified

run-as-lsf-helper String

Used internally by the test harness

script-opts String

Override options to the test case when running the tests (--dump-sql --no-commit)

Default value '' if not specified

time String

Write timelog sum to specified file

BARE-ARGS

(undocumented)

DESCRIPTION:

This command is like "prove" or "make test", running the test suite for the current namespace.