/ 
UR-0.47
River stage one • 2 direct dependents • 3 total dependents
⭐ Starred 3 GitHub stars
/ My::TAP::Parser::Iterator::Process::LSF
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 one or more test scripts

SYNOPSIS

# run everything in a given namespace
cd my_sandbox/TheNamespace
ur test run --recurse

# run only selected tests
cd my_sandbox/TheNamespace
ur test run My/Module.t Another/Module.t t/foo.t t/bar.t

# run only tests which load the TheNamespace::DNA module
cd my_sandbox/TheNamespace
ur test run --cover TheNamespace/DNA.pm

# run only tests which cover the changes you have in Subversion
cd my_sandbox/TheNamespace
ur test run --cover-svn-changes

# run 5 tests in parallel as jobs scheduled via LSF
cd my_sandbox/TheNamespace
 ur test run --lsf --jobs 5

DESCRIPTION

Runs a test harness around automated test cases, like "make test" in a make-oriented software distrbution, and similar to "prove" run in bulk.

When run w/o parameters, it looks for "t" directory in the current working directory, and runs ALL tests under that directory.

OPTIONS

--recurse
Run all tests in the current directory, and in sub-directories.  Without
--recurse, it will first recursively search for directories named 't' under
the current directory, and then recursively seatch for *.t files under those
directories.
--long
Include "long" tests, which are otherwise skipped in test harness execution
-v
Be verbose, meaning that individual cases will appear instead of just a full-script summary
--cover My/Module.pm
Looks in a special sqlite database which is updated by the cron which runs tests,
to find all tests which load My/Module.pm at some point before they exit.  Only
these tests will be run.

* you will still need the --long flag to run long tests.

* if you specify tests on the command-line, only tests in both lists will run

* this can be specified multiple times

--cover-TOOL-changes
TOOL can be svn, svk, or cvs.

The script will run either "svn status", "svk status", or "cvs -q up" on a parent
directory with "GSC" in it, and get all of the changes in your perl_modules trunk.
It will behave as though those modules were listed as individual --cover options.
--lsf
Tests should not be run locally, instead they are submitted as jobs to the
LSF cluster with bsub.
--lsf-params
Parameters given to bsub when sceduling jobs.  The default is
"-q short -R select[type==LINUX64]"
--jobs <number>
This many tests should be run in parallel.  If --lsf is also specified, then
these parallel tests will be submitted as LSF jobs.

PENDING FEATURES

automatic remote execution for tests requiring a distinct hardware platform
logging profiling and coverage metrics with each test