/ 
Squatting-0.83
River stage one • 7 direct dependents • 7 total dependents
/ Squatting::With::Log
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::With::Log - a simple error log for Squatting apps

SYNOPSIS

Adding simple logging to your Squatting app:

use App 'With::Log', 'On::CGI';

This will let log from within your controllers:

C(
  Day => [ '/(\d+)/(\d+)/(\d+)' ],
  get => sub {
    my ($self, $year, $month, $day) = @_;
    my $log = $self->log;
    $log->debug(" year: $year");
    $log->info ("month: $month");
    $log->warn ("  day: $day");
    # you also get $log->error and $log->fatal
    $self->render('day');
  }
)

DESCRIPTION

Squatting::With::Log provides a simple logging object that can be used from within your controllers to send messages to either a log file or STDERR for informational purposes. Typically, these messages would be useful during development and debugging but would be disabled for production use.

To use this module, pass the string 'With::Log' to the use statement that loads your Squatting app.

CONFIGURATION

Squatting apps may set the following values in their %CONFIG hash to control the behavior of this module.

with.log.path

This should be a string that specifies the full path to where you want the logs to be sent.

Example:

$CONFIG{'with.log.path'} = "/tmp/error_log";
with.log.levels

This should be a comma-separated string that lists all the log levels you want to enable.

Example: Only output messages with a log level of error or fatal.

$CONFIG{'with.log.levels'} = "error,fatal";

API

Object Construction

$log = Squatting::Log->new(\%config)

Configuration

$log->enable(@levels)

This method enables the list of log levels you send it.

$log->disable(@levels)

This method disables the list of log levels you send it.

Introspection

$log->is_debug

$log->is_info

$log->is_warn

$log->is_error

$log->is_fatal

These methods return true if their respective log levels are enabled.

Logging

$log->debug(@messages)

$log->info(@messages)

$log->warn(@messages)

$log->error(@messages)

$log->fatal(@messages)

These methods output the list of log messages you send it using the specified log level.

SEE ALSO

Catalyst::Log - The Squatting::Log API is the same as the Catalyst::Log API.