/ 
UR-0.47
River stage one • 2 direct dependents • 3 total dependents
⭐ Starred 3 GitHub stars
/ UR::Context::ObjectFabricator
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::Context::ObjectFabricator - Track closures used to fabricate objects from data sources

DESCRIPTION

Object Fabricators are closures that accept listrefs of data returned by data source iterators, take slices out of them, and construct UR objects out of the results. They also handle updating the query cache and merging changed DB data with previously cached objects.

UR::Context::ObjectFabricator objects are used internally by UR::Context, and not intended to be used directly.

METHODS

create_for_loading_template
my $fab = UR::Context::ObjectFabricator->create_for_loading_template(
              $context, $loading_tmpl_hashref, $template_data,
              $rule, $rule_template, $values, $dsx);

Returns an object fabricator instance that is able to construct objects of the rule's target class from rows of data returned by data source iterators. Object fabricators are used a part of the object loading process, and are called by UR::Context::get_objects_for_class_and_rule() to transform a row of data returned by a data source iterator into a UR object.

For each class involved in a get request, the system prepares a loading template that describes which columns of the data source data are to be used to construct an instance of that class. For example, in the case where a get() is done on a child class, and the parent and child classes store data in separate tables linked by a relation-property/foreign-key, then the query against the data source will involve and SQL join (for RDBMS data sources). That join will produce a result set that includes data from both tables.

The $loading_tmpl_hashref will have information about which columns of that result set map to which properties of each involved class. The heart of the fabricator closure is a list slice extracting the data for that class and assigning it to a hash slice of properties to fill in the initial object data for its class. The remainder of the closure is bookkeeping to keep the object cache ($UR::Context::all_objects_loaded) and query cache ($UR::Context::all_params_loaded) consistent.

The interaction of the object fabricator, the query cache, object cache pruner and object loading iterators that may or may not have loaded all their data requires that the object fabricators keep a list of changes they plan to make to the query cache instead of applying them directly. When the Underlying Context Loading iterator has loaded the last row from the Data Source Iterator, it calls finalize() on the object fabricator to tell it to go ahead and apply its changes; essentially treating that data as a transaction.

all_object_fabricators
my @fabs = UR::Context::ObjectFabricator->all_object_fabricators();

Returns a list of all object fabricators that have not yet been finalized

fabricate
my $ur_object = $fab->fabricate([columns,from,data,source]);

Given a listref of data pulled from a data source iterator, it slices out the appropriate columns from the list and constructs a single object to return.

is_loading_in_progress_for_boolexpr
my $bool = $fab->is_loading_in_progress_for_boolexpr($boolexpr);

Given a UR::BoolExpr instance, it returns true if the given fabricator is prepared to construct objects matching this boolexpr. This is used by UR::Context to know if other iterators are still pulling in objects that could match another iterator's boolexpr, and it should therefore not trust that the object cache is conplete.

finalize
$fab->finalize();

Indicates to the iterator that the caller is done using it for constructing objects, probably because the data source has no more data or the iterator that was using this fabricator has gone out of scope.

apply_all_params_loaded
$fab->apply_all_params_loaded();

As the fabricator constructs objects, it buffers changes to all_params_loaded (the Context's query cache) to maintain consistency if multiple iterators are working concurrently. At the appripriate time, call apply_all_params_loaded() to take those changes and apply them to the current Context's all_params_loaded.