/ 
Squatting-0.83
River stage one • 7 direct dependents • 7 total dependents
/ Squatting::On::Continuity
Security Advisories (9)
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

Squatting::On::Continuity - use Continuity as the server for your Squatting app

SYNOPSIS

Running a Squatting application on top of Continuity:

use App 'On::Continuity';
App->init;
App->continue(port => 2012);

DESCRIPTION

The purpose of this module is to add a continue method to your app that will start a Continuity-based web server when invoked. To use this module, pass the string 'On::Continuity' to the use statement that loads your Squatting app.

API

Continuity meets MVC (or just VC, actually)

App->continue(%options)

This method starts a Continuity-based web server. The %options are passed straight through to Continuity, and they let you specify things like what port to run the server on.

EXPLANATION

The Special Powers of Continuity

Continuity has 2 highly unusual (but useful) capabilities.

1. It can hold many simultaneous HTTP connections open.
2. It can "pause" execution until the next request comes in.

The easiest way to explain this is by example.

Becoming RESTless

Consider this controller which has an infinite loop in it.

C(
  Count => [ '/@count' ],
  get => sub {
    my ($self) = @_;
    my $cr     = $self->cr;
    my $i      = 1;
    while (1) {
      $cr->print($i++);
      $cr->next;
    }
  },
  continuity => 1,
)

Here, the code is dropping down to the Continuity level. The $cr variable contains a Continuity::Request object, and with that in hand, we can try something as audacious as an infinite loop. However, this while loop does not spin out of control and eat up all your CPU. The $cr->next statement will pause execution of the current coroutine, and it will wait until the next HTTP request to come in. Thus, you can hit reload multiple times and watch $i increment each time.

However, not just any HTTP request will wake this coroutine up. To make $cr->next stop blocking, a request with the following properties will have to come in.

It has to have the same session_id.
It has to be for the same controller.
It has to be a GET request.

The key is this line:

queue => { get => 'name_of_queue' }

When you're squatting on Continuity, you're allowed to define your controllers with a queue attribute. It should contain a hashref where the keys are HTTP methods (in lower case) and the values are unique strings that will be used internally by Continuity to differentiate one queue of requests from another.

Every method mentioned in queue will be given its own coroutine to run in.

Pausing for Other Events

TO BE CONTINUED...

For a sneak peak, take a look at the Chat application in the eg/ directory.

SEE ALSO

Coro, Continuity, Continuity::Mapper, Squatting::Mapper