/ 
App-Netdisco-2.007000_002
⭐ Starred 676
/ App::Netdisco::Web::Plugin
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

App::Netdisco::Web::Plugin - Plugin subsystem for App::Netdisco Web UI components

Introduction

App::Netdisco's plugin subsystem allows the user more control of Netdisco UI components displayed in the web browser. Plugins can be distributed independently from Netdisco and are a better alternative to source code patches.

The following UI components are implemented as plugins:

  • Navigation Bar items (e.g. Inventory link)

  • Tabs for Search and Device pages

  • Reports (pre-canned searches)

This document explains how to configure which plugins are loaded. See App::Netdisco::Manual::WritingPlugins if you want to develop new plugins.

Application Configuration

In the main config.yml file for App::Netdisco (located in share/...) you'll find the web_plugins configuration directive. This lists, in YAML format, a set of Perl module names (or partial names) which are the plugins to be loaded. For example:

web_plugins:
  - Inventory
  - Report::DuplexMismatch
  - Search::Device
  - Search::Node
  - Search::Port
  - Device::Details
  - Device::Ports

When the name is specified as above, App::Netdisco automatically prepends "App::Netdisco::Web::Plugin::" to the name. This makes, for example, App::Netdisco::Web::Plugin::Inventory. This is the module which is loaded to add a user interface component.

Such plugin modules can either ship with the App::Netdisco distribution itself, or be installed separately. Perl uses the standard @INC path searching mechanism to load the plugin modules.

If an entry in the web_plugins list starts with a "+" (plus) sign then App::Netdisco attemps to load the module as-is, without prepending anything to the name. This allows you to have App::Netdiso web UI plugins in other namespaces:

web_plugins:
  - Inventory
  - Search::Device
  - Device::Details
  - +My::Other::Netdisco::Web::Component

The order of the entries in web_plugins is significant. Unsurprisingly, the modules are loaded in order. Therefore Navigation Bar items appear in the order listed, and Tabs appear on the Search and Device pages in the order listed.

The consequence of this is that if you want to change the order (or add or remove entries) then simply edit the web_plugins setting. In fact, we recommend adding this setting to your <environment>.yml file and leaving the config.yml file alone. Your Environment's version will take prescedence.

Finally, if you want to add components without completely overriding the web_plugins setting, use the extra_web_plugins setting instead in your Environment configuration. Any Navigation Bar items or Page Tabs are added after those in web_plugins.