/ 
Squatting-0.83
River stage one • 7 direct dependents • 7 total dependents
/ Squatting::View
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::View - default view class for Squatting

SYNOPSIS

package App::Views;
use Squatting ':views';
our @V = (
  V(
    'example',
    layout => sub {
      my ($self, $v, $content) = @_;
      "(header $content footer)";
    },
    home => sub {
      my ($self, $v) = @_;
      "Hello, $v->{name}";
    },
    _ => sub {
      my ($self, $v) = @_;
      "You tried to render $self->{template} which was not defined.";
    },
    arbitrary_data => [ { is => 'ok' }, 2 ],
  )
);

DESCRIPTION

In Squatting, views are objects that contain many templates. Templates are represented by coderefs that will be treated as methods of a view object. The job of a template is to take a hashref of variables and return a string.

Typically, the hashref of variables will be the same as what's in $controller->v. This is important to note, because if you want a session variable in $controller->state to affect the template, you have to put it in $controller->v.

API

General Methods

$view = Squatting::View->new($name, %methods)

The constructor takes a name and a hash of attributes and coderefs. Note that the name must be unique within the package the view is defined.

$view->name

This returns the name of the view.

$view->headers

This returns a hashref of the outgoing HTTP headers.

Template Methods

$content = $view->$template($v)

Any coderef that was given to the constructor may be called by name. Templates should be passed in a hashref ($v) with variables for it to use to generate the final output.

$content = $view->layout($v, $content)

If you define a template named "layout", it'll be used to wrap the content of all templates whose name do not begin with "_". You can use this feature to provide standard headers and footers for your pages.

$content = $view->_($v)

If you define a template named "_", this will act as a catch-all that can be asked to render anything that wasn't explicitly defined. It's like our version of AUTOLOAD.

NOTE: You can find out what they tried to render by inspecting $self->{template}.

This feature is useful when you're using a file-based templating system like Tenjin or Template Toolkit, and you don't want to write a template sub for every single template. Instead, you can make $self->{template} correspond to a file on disk.

$view->{$template} = \&coderef

You are allowed to directly replace the template coderefs with your own. The most common reason you'd do this would be to replace an app's default layout with your own.

$view->{layout} = sub {
  my ($self, $v, $content) = @_;
  # ...
};

SEE ALSO

Squatting, Squatting::Controller