/ 
UR-0.47
River stage one • 2 direct dependents • 3 total dependents
⭐ Starred 3 GitHub stars
/ Command::DynamicSubCommands
Security Advisories (11)
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.

NAME

Command::DynamicSubCommands - auto-generate sub-commands based on other classes

SYNOPSIS

# given that these classes exist:
#   Acme::Task::Foo
#   Acme::Task::Bar

# in Acme/Worker/Command/DoTask.pm:

   class Acme::Worker::Command::DoTask {
       is => 'Command::DynamicSubCommands',
       has => [
           param1 => { is => 'Text' },
           param2 => { is => 'Text' },
       ]
   };

   sub _sub_commands_from { 'Acme::Task' }

   sub execute {
       my $self = shift;
       print "this command " . ref($self) . " applies to " . $self->_target_class_name;
       return 1;
   }

# the class above will discover them at compile, 
# and auto-generate these subclasses of itself:
#   Acme::Worker::Command::DoTask::Foo
#   Acme::Worker::Command::DoTask::Bar

# in the shell...
#
#   $ acme worker do-task
#   foo
#   bar
#
#   $ acme worker do-task foo --param1 aaa --param2 bbb 
#   this command Acme::Worker::Command::DoTask::Foo applies to Acme::Task::Foo
#
#   $ acme worker do-task bar --param1 ccc --param2 ddd
#   this command Acme::Worker::Command::DoTask::Bar applies to Acme::Task::Bar

DESCRIPTION

This module helps you avoid writing boilerplate commands.

When a command has a set of sub-commands which are meant to be derived from another group of classes, this module lets you auto-generate those sub-commands at run time.

REQUIRED ABSTRACT METHOD

_sub_commands_from
$base_namespace = Acme::Order::Command->_sub_commands_from();
# 'Acme::Task

Returns the namespace from which target classes will be discovered, and
sub-commands will be generated.

PRIVATE API

_target_class_name
$c= Acme::Order::Command::Purchasing->_target_class_name;
# 'Acme::Task::Foo'

The name of some class under the _sub_commands_from() namespace.
This value is set during execute, revealing which sub-command the caller is using.

OPTIONAL OVERRIDES

_build_sub_commmand
This can be overridden to customize the sub-command construction.
By default, each target under _sub_commands_from will result in 
a call to this method.  The default implementation is below:

my $self = shift;
my ($suggested_class_name,$delegator_class_name,$target_class_name) = @_;

class {$suggested_class_name} { 
    is => $delegator_class_name, 
    sub_classify_by => 'class',
    has_constant => [
        _target_class_name => { value => $target_class_name },
    ]
};

return ($suggested_class_name);

Note that the class in question may be on the filesystem, and not need
to be created.  The return list can include more than one class name,
or zero class names.
_build_all_sub_commands
This is called once for any class which inherits from Command::DynamicSubCommands.

It generates the sub-commands as needed, and returns a list.

By default it resolves the target classes, and calls  _build_sub_command

It can be overridden to customize behavior, or filter results.  Be sure
to call @cmds = $self->SUPER::_build_all_sub_commands() if you want 
to get the default commands in addition to overriding.

The sub-commands need not be 1:1 with the target classes, though this is the default.

The sub-commands need not inherit from the Command::DynamicSubCommands base command which generates them, though this is the default.