/ 
UR-0.47
River stage one • 2 direct dependents • 3 total dependents
⭐ Starred 3 GitHub stars
/ UR::Service::RPC::Executer
Security Advisories (11)
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.

NAME

UR::Service::RPC::Executer - Base class for modules implementing RPC executers

DESCRIPTION

This class is an abstract base class used to implement RPC executers. That is, modules meant to have their methods called from another process, and have the results passed back to the original caller. The communication happens over a read-write filehandle such as a socket by passing UR::Service::RPC::Message objects back and forth.

Executors are subordinate to a UR::Service::RPC::Server object which handles decoding the message passed over the socket, calling the method on the correct executor in the right context, and returning the result back through the file handle.

PROPERTIES

fh => IO::Handle

File handle messages are received on and responses are sent to

use_sigio => Boolean

If true, the Server will set up a callback on the IO signal to handle execution, so the Server does not need to block in loop().

METHODS

authenticate
$bool = $exec->authenticate($msg);

This is called by execute() after the message object is deserialized from the filehandle. The default implementation just returns true. Subclasses can override this to examine the UR::Service::RPC::Message object and return true or fale whether it should allow or disallow execution. If authentication fails, the Executor should modify the Message object in-place with a proper return value and exception.

execute
$exec->execute();

Called when the Server detects data is available to read on its file handle. It deserializes the message and calls authenticate. If authentication fails, it immediately passes the message object back to the caller.

If authentication succeeds, it calls the appropriate method in the Executor package, and creates a new Message object with the return value to pass back to the caller.

close_connection
$exec->close_connection();

Called by execute() when it detects that the file handle has closed.

Derived classes should define additional methods that then become callable by execute().

SEE ALSO

UR::Service::RPC::Server, UR::Service::RPC::Message