/ 
App-Netdisco-2.044005
River stage one • 1 direct dependent • 1 total dependent
⭐ Starred 676 GitHub stars
/ App::Netdisco::DB::ExplicitLocking
Security Advisories (10)
CVE-2022-24785 (2022-04-04)

Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.

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

App::Netdisco::DB::ExplicitLocking - Support for PostgreSQL Lock Modes

SYNOPSIS

In your DBIx::Class schema:

package My::Schema;
__PACKAGE__->load_components('+App::Netdisco::DB::ExplicitLocking');

Then, in your application code:

use App::Netdisco::DB::ExplicitLocking ':modes';
$schema->txn_do_locked($table, MODE_NAME, sub { ... });

This also works for the ResultSet:

package My::Schema::ResultSet::TableName;
__PACKAGE__->load_components('+App::Netdisco::DB::ExplicitLocking');

Then, in your application code:

use App::Netdisco::DB::ExplicitLocking ':modes';
$schema->resultset('TableName')->txn_do_locked(MODE_NAME, sub { ... });

DESCRIPTION

This DBIx::Class component provides an easy way to execute PostgreSQL table locks before a transaction block.

You can load the component in either the Schema class or ResultSet class (or both) and then use an interface very similar to DBIx::Class's txn_do().

The package also exports constants for each of the table lock modes supported by PostgreSQL, which must be used if specifying the mode (default mode is ACCESS EXCLUSIVE).

EXPORTS

With the :modes tag (as in SYNOPSIS above) the following constants are exported and must be used if specifying the lock mode:

  • ACCESS_SHARE

  • ROW_SHARE

  • ROW_EXCLUSIVE

  • SHARE_UPDATE_EXCLUSIVE

  • SHARE

  • SHARE_ROW_EXCLUSIVE

  • EXCLUSIVE

  • ACCESS_EXCLUSIVE

METHODS

$schema->txn_do_locked($table|\@tables, MODE_NAME?, $subref)

This is the method signature used when the component is loaded into your Schema class. The reason you might want to use this over the ResultSet version (below) is to specify multiple tables to be locked before the transaction.

The first argument is one or more tables, and is required. Note that these are the real table names in PostgreSQL, and not DBIx::Class ResultSet aliases or anything like that.

The mode name is optional, and defaults to ACCESS EXCLUSIVE. You must use one of the exported constants in this parameter.

Finally pass a subroutine reference, just as you would to the normal DBIx::Class txn_do() method. Note that additional arguments are not supported.

$resultset->txn_do_locked(MODE_NAME?, $subref)

This is the method signature used when the component is loaded into your ResultSet class. If you don't yet have a ResultSet class (which is the default - normally only Result classes are created) then you can create a stub which simply loads this component (and inherits from DBIx::Class::ResultSet).

This is the simplest way to use this module if you only want to lock one table before your transaction block.

The first argument is the optional mode name, which defaults to ACCESS EXCLUSIVE. You must use one of the exported constants in this parameter.

The second argument is a subroutine reference, just as you would pass to the normal DBIx::Class txn_do() method. Note that additional arguments are not supported.