/ 
YATT-Lite-0.101_102
/ YATT::Lite::WebMVC0::Partial::Session2
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

YATT::Lite::WebMVC0::Partial::Session2 -- (Revised) Session support for YL

SYNOPSIS

In app.psgi:

use YATT::Lite::WebMVC0::SiteApp -as_base; # As usual.
#
# Below imports definitions of &yatt:session_start(); and
# session_state/session_store options with multiple inheritance.
#
use YATT::Lite::WebMVC0::Partial::Session2 -as_base;
#
# Then create site app as usual.
#
use Plack::Session::State::Cookie ();
use Plack::Session::Store::DBI ();
#
my MY $site = MY->load_factory_for_psgi(
  $0,
  doc_root => "$FindBin::Bin/public",

  session_state => Plack::Session::State::Cookie->new(),
  session_store => [DBI => get_dbh => sub { DBI->connect(...) } ],
);
#
return $site->to_app;

In *.yatt:

&yatt:session_start(); # Optional

<h2>Hello &yatt:psgix_session(){user};</h2>

DESCRIPTION

This module is a session plugin for site apps of YATT::Lite, based on Plack::Session family.

Internally, it creates Plack::Middleware::Session at startup. Then it emulates Plack::Middleware::Session#get_session on each call to &yatt:session_start(); and emulates Plack::Middleware::Session#finalize on response finalization.

OPTIONS

Following options are imported to the site app.

session_state = Plack::Session::State::Cookie | [$NAME => @ARGS]

This option can take one value of following two types:

An instance of Plack::Session::State::Cookie compatible object.
An ARRAY which consists of [$NAME, @ARGS]

In this case, $NAME is used to load specific session state class using Plack::Util::load_class($NAME, 'Plack::Session::State').

If no option is provided the default Plack::Session::State::Cookie will be used.

session_store = Plack::Session::Store | [$NAME => @ARGS]

This option can take one value of following two types:

An instance of Plack::Session::Store compatible object.
An ARRAY which consists of [$NAME, @ARGS]

In this case, $NAME is used to load specific session state class using Plack::Util::load_class($NAME, 'Plack::Session::Store').

If no option is provided the default Plack::Session::Store will be used.

session_middleware_class = $CLASS_NAME

ENTITY FUNCTIONS

session_start

Explicitly start session. psgix_session calls this automatically.

session_state_id

Extract state id from cookie without starting session. Returns undef if not exists.

session_state_exists

Test if session state id exists.

Raw psgix.session interface

psgix_session

$env->{psgix.session}

psgix_session_options

$env->{psgix.session.options}

psgix_session_exists

$env->{psgix.session.options}{id}

plack.session (Plack::Session) interface

session

$env->{plack.session}

session_id

Plack::Session->id()

session_get

Plack::Session->get()

session_set

Plack::Session->set()

session_remove

Plack::Session->remove()

session_keys

Plack::Session->keys()

session_expire

Plack::Session->expire()

SEE ALSO

Plack::Session::State::Cookie, Plack::Session::Store

AUTHOR

hkoba