/ 
YATT-Lite-0.0_6
/ YATT::Lite
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 - Yet Another Template Toolkit, Lightweight rewrite.

SYNOPSIS

# Minimum case:
use YATT::Lite;

my $tmpl = q{
  <!yatt:args title who="?World">
  <h2>&yatt:title;</h2>
  Hello &yatt:who;!

  <!yatt:widget alter title who="?Space">
  <div class="title">&yatt:title;</div>
  <div class="body">
  Hello &yatt:who;!
  </div>
};

my $yatt = new YATT::Lite(vfs => [data => $tmpl], app_ns => "MyApp");

print $yatt->render("", {title => "My First YATT"}), "\n";
# or
$yatt->render_into(\*STDOUT, alter => ["My Second YATT"]);

# Multiple template.
my $yatt2 = new YATT::Lite(vfs => [data => {foo => "..", bar => ".."}]
                           , app_ns => "MyApp2");
print $yatt2->render(foo => [1,2]);
print $yatt2->render(bar => [3,4]);

# And filesystem based templating.
my $yatt3 = new YATT::Lite(vfs => [file => "my.yatt"], app_ns => "MyApp3");
my $yatt4 = new YATT::Lite(vfs => [dir  => "my.ytmpl"], app_ns => "MyApp4");

DESCRIPTION

YATT is Yet Another Template Toolkit, aimed at Web Designers, rather than well-trained programmers. To achieve this goal, YATT provides more readable syntax for HTML/XML savvy designers, ``lint'' for static syntax checking and many safer default behaviors, ie. automatic output escaping based on argument type declaration and file extension based visibility handling of template.

YATT::Lite is template-syntax-compatible, lightweight, full rewrite of YATT with superior functionalities.

In YATT, basic building block is called ``widget''. Template text is treated as a sequence of ``widget definition'', each of which is leaded by ``widget declaration: <!yatt:widget>'', like multipart email.

A widget is translated into a perl subroutine (on memory, currently). A template text is translated into a perl package (class). The translation is per-template basis and occurs on demand of widget. Template can be given to YATT::Lite as a data(string/hash), filename or directory name.

Package name of template is automatically generated with respect to option and filepath. If template is loaded from filesystem, it is cached and reloaded if modified.

Although widget is basically 'named', head of each template text can be a ``unnamed (default) widget'', so that designers can treat a template file itself as a widget. This means plain HTML files *just works* as template set.

In future, mainline YATT will incorporate YATT::Lite interface. It means, today, if you want to adapt next generation YATT before its release, write your script using YATT::Lite.

This is (still) alpha release. Although template syntax and facade(YATT::Lite) API became stable (I want), internal modules are *open* for discussion.

INSTALLATION

It's all pure Perl, so it's ok to put the .pm files (or git repo itself) in their appropriate perl @INC path. (But see "NON-STANDARD DIRECTORY STRUCTURE")

The easiest way to use this distribution in your project is:

git clone git://github.com/hkoba/yatt_lite.git lib/YATT

# or If your project is managed in git, clone as submodule like this:

git submodule add git://github.com/hkoba/yatt_lite.git lib/YATT
git submodule init
git submodule update

Then you can use sample app.psgi to start yatt-enabled webapp, like this:

cp lib/YATT/samples/app.psgi .
mkdir html
plackup

Now you are ready to write your first index.yatt. Open your favorite editor and create html/index.yatt like this:

<!yatt:args x y>
<h2>Hello &yatt:x; world!</h2>
&yatt:y;

Then try to access:

http://0:5000/
http://0:5000/?x=foo
http://0:5000/?x=foo&y=bar

NON-STANDARD DIRECTORY STRUCTURE

Unfortunately, YATT::Lite distribution doesn't conform normal CPAN style structure. This is experimental, but intentional. Because:

1 I want to embed YATT::Lite into other git repo as submodule. Use of git submodule greatly helps development.

To allow this, all modules are placed under topdir of the distribution.

2 Engine(modules), support scripts and tests should be bundled together.

To achieve this, scripts/* and elisp/* is placed in YATT/.

3 Also, I want to bundle ready-to-run samples.

To achieve this, redundant lib/ directory and symbolically lib/YATT is linked to to dist topdir.

This means YATT::Lite distribution has cycle of symbolic link. Please take care.

SUPPORT AND DOCUMENTATION

You can also look for Source Code Repository at:

https://github.com/hkoba/yatt_lite
git://github.com/hkoba/yatt_lite.git

AUTHOR

"KOBAYASI, Hiroaki" <hkoba@cpan.org>

COPYRIGHT AND LICENCE

Copyright (C) 2007..2012 "KOBAYASI, Hiroaki"

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.