/ 
App-Netdisco-2.039021
⭐ Starred 676
/ App::Netdisco::Worker::Plugin::MakeRancidConf
Security Advisories (10)
CVE-2022-24785 (2022-04-04)

Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.

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

MakeRancidConf - Generate RANCID Configuration

INTRODUCTION

This worker will generate a RANCID configuration for all devices in Netdisco.

Optionally you can provide configuration to control the output, however the defaults are sane, and will create one RANCID group called "default" which contains all devices. Those devices not discovered successfully within the past day will be marked as "down" for RANCID to skip. Configuration is saved to the "rancid" subdirectory of Netdisco's home folder.

You could run this worker at 09:05 each day using the following configuration:

schedule:
  makerancidconf:
    when: '5 9 * * *'

CONFIGURATION

Here is a complete example of the configuration, which must be called "rancid". All keys are optional:

rancid:
  rancid_home:  "$ENV{NETDISCO_HOME}/rancid" # default
  down_age:     '1 day'                      # default
  delimiter:    ':'                          # default
  groups:
    groupname1: 'host_group1_acl'
    groupname2: 'host_group2_acl'
  vendormap:
    vname1:     'host_group3_acl'
    vname2:     'host_group4_acl'
  by_ip:        'host_group5_acl'
  by_hostname:  'host_group6_acl'

Note that the default home for writing files is not "/var/lib/rancid" so you may wish to set this (especially if migrating from the old netdisco-rancid-export script).

Any values above that are a Host Group ACL will take either a single item or list of Network Identifiers or Device Properties. See the ACL documentation wiki page for full details. We advise you to use the "host_groups" setting and then refer to named entries in that, for example:

host_groups:
  coredevices: '192.0.2.0/24'
  edgedevices: '172.16.0.0/16'

rancid:
  groups:
    core_devices: 'group:coredevices'
    edge_devices: 'group:edgedevices'

rancid_home

The location to write RANCID Group configuration files into. A subdirectory for each Group will be created.

down_age

This should be the same or greater than the interval between regular discover jobs on your network. Devices which have not been discovered within this time will be marked as "down" to RANCID.

The format is any time interval known and understood by PostgreSQL, such as at https://www.postgresql.org/docs/8.4/static/functions-datetime.html.

delimiter

Set this to the delimiter character if needed to be different from the default.

groups

This dictionary maps RANCID Group names with configuration which will match devices in the Netdisco database.

The left hand side (key) should be the RANCID group name, the right hand side (value) should be a Netdisco ACL to select devices in the Netdisco database.

vendormap

If the device Vendor in Netdisco is not the same as the RANCID vendor script, configure a mapping here.

The left hand side (key) should be the RANCID vendor, the right hand side (value) should be a Netdisco ACL to select devices in the Netdisco database.

by_ip

Netdisco ACL to select devices which will be written to the RANCID config as an IP address, instead of the DNS FQDN or SNMP host name.

by_hostname

Netdisco ACL to select devices which will have the unqualified host name written to the RANCID config. This is done simply by stripping the domain_suffix configuration setting from the device FQDN.

SEE ALSO

1 POD Error

The following errors were encountered while parsing the POD:

Around line 98:

Non-ASCII character seen before =encoding in '# default'. Assuming UTF-8