/ 
App-Netdisco-2.034002
/ netdisco-rancid-export
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

netdisco-rancid-export - Generate RANCID Group Configuration

CONFIGURATION

This script requires some configuration to be added to your Netdisco "~/environments/deployment.yml" file, for example:

rancid:
  rancid_home:  /var/lib/rancid
  down_age:     '1 day'
  delimiter:    ':'
  by_ip:        [ other ]
  by_hostname:  [ other2 ]
  groups:
    switch:     [ 'name:.*[Ss][Ww].*' ]
    rtr:        [ 'name:[rR]tr.*' ]
    ap:         [ 'name:[aA][pP].*' ]
  vendormap:
    "dell":      force10
    "dell:2024": dellnseries

Note that netdisco-rancid-export is not part of the automatic scheduler built in to Netdisco. You should run this script via cron just after your periodic discoverall.

rancid_home

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

Default: "/var/lib/rancid".

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.

Default: "1 day".

delimiter

RANCID version 3 uses a semicolon as delimiter. Set this to the delimiter character if needed to be different from the default.

Default: ":".

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 Netdisco vendor, the right hand side (value) should be the RANCID vendor script name. You can also set the Netdisco vendor to be "vendor:model" for fine-grained control. See the synopsis for an example.

groups

This dictionary maps RANCID Group names with configuration which will match devices in the Netdisco database. The configuration is the same as any of Netdisco's "*_only" settings, and accepts IP, prefix, device property.

by_ip

List of RANCID Groups which will have Device IPs written to the RANCID configuration file, instead of DNS or SNMP host names.

by_hostname

List of RANCID Groups which will have Device Hostname written to the RANCID configuration file, instead of FQDN. This is done simply by stripping the domain_suffix configuration item from the FQDN.

SEE ALSO