Homepage

org.webjars.npm:node-forge@0.7.5 vulnerabilities

  • latest version

    1.3.1

  • latest non vulnerable version

    1.3.1

  • first published

    10 years ago

  • latest version published

    2 years ago

  • licenses detected

  • package registry

    View on Maven Central Repository
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the org.webjars.npm:node-forge package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Improper Verification of Cryptographic Signature

    org.webjars.npm:node-forge is a WebJar for node-forge.

    Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature due to RSA's PKCS#1 v1.5 signature verification code which does not properly check DigestInfo for a proper ASN.1 structure. This can lead to successful verification with signatures that contain invalid structures but a valid digest.

    How to fix Improper Verification of Cryptographic Signature?

    Upgrade org.webjars.npm:node-forge to version 1.3.1 or higher.

    [,1.3.1)
    • M
    Improper Verification of Cryptographic Signature

    org.webjars.npm:node-forge is a WebJar for node-forge.

    Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature due to RSAs PKCS#1` v1.5 signature verification code which is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used.

    How to fix Improper Verification of Cryptographic Signature?

    Upgrade org.webjars.npm:node-forge to version 1.3.1 or higher.

    [,1.3.1)
    • H
    Improper Verification of Cryptographic Signature

    org.webjars.npm:node-forge is a WebJar for node-forge.

    Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature due to RSA's PKCS#1 v1.5 signature verification code which does not check for tailing garbage bytes after decoding a DigestInfo ASN.1 structure. This can allow padding bytes to be removed and garbage data added to forge a signature when a low public exponent is being used.

    How to fix Improper Verification of Cryptographic Signature?

    Upgrade org.webjars.npm:node-forge to version 1.3.1 or higher.

    [,1.3.1)
    • M
    Prototype Pollution

    org.webjars.npm:node-forge is a WebJar for node-forge.

    Affected versions of this package are vulnerable to Prototype Pollution via the forge.debug API if called with untrusted input.

    How to fix Prototype Pollution?

    Upgrade org.webjars.npm:node-forge to version 1.3.1 or higher.

    [,1.3.1)
    • M
    Open Redirect

    org.webjars.npm:node-forge is a WebJar for node-forge.

    Affected versions of this package are vulnerable to Open Redirect via parseUrl function when it mishandles certain uses of backslash such as https:/\/\/\ and interprets the URI as a relative path.

    PoC:

    
// poc.js
var forge = require("node-forge");
var url = forge.util.parseUrl("https:/\/\/\www.github.com/foo/bar");
console.log(url);

// Output of node poc.js:

{
  full: 'https://',
  scheme: 'https',
  host: '',
  port: 443,
  path: '/www.github.com/foo/bar',                        <<<---- path  should be "/foo/bar"
  fullHost: ''
}

    How to fix Open Redirect?

    Upgrade org.webjars.npm:node-forge to version 1.3.1 or higher.

    [,1.3.1)
    • H
    Prototype Pollution

    org.webjars.npm:node-forge is a WebJar for node-forge.

    Affected versions of this package are vulnerable to Prototype Pollution via the util.setPath function.

    Note: version 0.10.0 is a breaking change removing the vulnerable functions.

    POC:

    const nodeforge = require('node-forge');
var obj = {};
nodeforge.util.setPath(obj, ['__proto__', 'polluted'], true);
console.log(polluted);

    How to fix Prototype Pollution?

    Upgrade org.webjars.npm:node-forge to version 1.3.1 or higher.

    [,1.3.1)
    Go back to all versions of this package