3 via 3 paths





Find, fix and prevent vulnerabilities in your code.

  • 1
  • 2
  • 3
  • 0
  • 0

high severity

Signature Validation Bypass

  • Vulnerable module: xml-crypto
  • Introduced through: xml-crypto@0.8.5

Detailed paths

  • Introduced through: node-wsdl@1.0.1 xml-crypto@0.8.5
    Remediation: Upgrade to xml-crypto@2.0.0.


xml-crypto is a xml digital signature and encryption library for Node.js.

Affected versions of this package are vulnerable to Signature Validation Bypass. An attacker can inject an HMAC-SHA1 signature that is valid using only knowledge of the RSA public key. This allows bypassing signature validation.


Upgrade xml-crypto to version 2.0.0 or higher.


medium severity

Arbitrary Code Injection

  • Vulnerable module: ejs
  • Introduced through: ejs@2.5.9

Detailed paths

  • Introduced through: node-wsdl@1.0.1 ejs@2.5.9
    Remediation: Upgrade to ejs@3.1.6.


ejs is a popular JavaScript templating engine.

Affected versions of this package are vulnerable to Arbitrary Code Injection via the render and renderFile. If external input is flowing into the options parameter, an attacker is able run arbitrary code. This include the filename, compileDebug, and client option.


let ejs = require('ejs')
    filename:'/etc/passwd\nfinally {\'child_process\').execSync(\'touch EJS_HACKED\') }',
    compileDebug: true,
    message: 'test',
    client: true


Upgrade ejs to version 3.1.6 or higher.


medium severity

XML External Entity (XXE) Injection

  • Vulnerable module: xmldom
  • Introduced through: xml-crypto@0.8.5

Detailed paths

  • Introduced through: node-wsdl@1.0.1 xml-crypto@0.8.5 xmldom@0.1.19
    Remediation: Upgrade to xml-crypto@2.1.0.


xmldom is an A pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module.

Affected versions of this package are vulnerable to XML External Entity (XXE) Injection. Does not correctly preserve system identifiers, FPIs or namespaces when repeatedly parsing and serializing maliciously crafted documents.


XXE Injection is a type of attack against an application that parses XML input. XML is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. By default, many XML processors allow specification of an external entity, a URI that is dereferenced and evaluated during XML processing. When an XML document is being parsed, the parser can make a request and include the content at the specified URI inside of the XML document.

Attacks can include disclosing local files, which may contain sensitive data such as passwords or private user data, using file: schemes or relative paths in the system identifier.

For example, below is a sample XML document, containing an XML element- username.

<?xml version="1.0" encoding="ISO-8859-1"?>

An external XML entity - xxe, is defined using a system identifier and present within a DOCTYPE header. These entities can access local or remote content. For example the below code contains an external XML entity that would fetch the content of /etc/passwd and display it to the user rendered by username.

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE foo [
   <!ENTITY xxe SYSTEM "file:///etc/passwd" >]>

Other XXE Injection attacks can access local resources that may not stop returning data, possibly impacting application availability and leading to Denial of Service.


Upgrade xmldom to version 0.5.0 or higher.