Vulnerabilities

12 via 25 paths

Dependencies

335

Source

GitHub

Commit

2527708c

Find, fix and prevent vulnerabilities in your code.

Severity
  • 1
  • 4
  • 7
Status
  • 12
  • 0
  • 0

critical severity

Predictable Value Range from Previous Values

  • Vulnerable module: form-data
  • Introduced through: @salesforce/core@2.37.1 and @salesforce/command@3.1.3

Detailed paths

  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/core@2.37.1 jsforce@1.11.1 request@2.88.2 form-data@2.3.3
  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/command@3.1.3 @salesforce/core@2.37.1 jsforce@1.11.1 request@2.88.2 form-data@2.3.3

Overview

Affected versions of this package are vulnerable to Predictable Value Range from Previous Values via the boundary value, which uses Math.random(). An attacker can manipulate HTTP request boundaries by exploiting predictable values, potentially leading to HTTP parameter pollution.

Remediation

Upgrade form-data to version 2.5.4, 3.0.4, 4.0.4 or higher.

References

high severity

Improper Link Resolution Before File Access ('Link Following')

  • Vulnerable module: tar-fs
  • Introduced through: puppeteer@10.4.0

Detailed paths

  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 puppeteer@10.4.0 tar-fs@2.0.0
    Remediation: Upgrade to puppeteer@18.2.0.

Overview

tar-fs is a filesystem bindings for tar-stream.

Affected versions of this package are vulnerable to Improper Link Resolution Before File Access ('Link Following') through the exports.extract function. An attacker can manipulate the path of extracted files to write outside the intended directory by crafting a malicious tarball.

Workaround

This vulnerability can be mitigated by using the ignore option to ignore paths like symlinks that are not files/directories.

  ignore (_, header) {
    // pass files & directories, ignore e.g. symlinks
    return header.type !== 'file' && header.type !== 'directory'
  }

Details

A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.

Directory Traversal vulnerabilities can be generally divided into two types:

  • Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.

st is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public route.

If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.

curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa

Note %2e is the URL encoded version of . (dot).

  • Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as Zip-Slip.

One way to achieve this is by using a malicious zip archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.

The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:

2018-04-15 22:04:29 .....           19           19  good.txt
2018-04-15 22:04:42 .....           20           20  ../../../../../../root/.ssh/authorized_keys

Remediation

Upgrade tar-fs to version 1.16.5, 2.1.3, 3.0.9 or higher.

References

high severity

Symlink Attack

  • Vulnerable module: tar-fs
  • Introduced through: puppeteer@10.4.0

Detailed paths

  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 puppeteer@10.4.0 tar-fs@2.0.0
    Remediation: Upgrade to puppeteer@18.2.0.

Overview

tar-fs is a filesystem bindings for tar-stream.

Affected versions of this package are vulnerable to Symlink Attack via the extraction process of a maliciously crafted tar file. An attacker can overwrite or write unauthorized files outside the intended directory by exploiting the path traversal and link following vulnerabilities.

Remediation

Upgrade tar-fs to version 1.16.4, 2.1.2, 3.0.7 or higher.

References

high severity

Denial of Service (DoS)

  • Vulnerable module: ws
  • Introduced through: puppeteer@10.4.0

Detailed paths

  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 puppeteer@10.4.0 ws@7.4.6
    Remediation: Upgrade to puppeteer@18.2.0.

Overview

ws is a simple to use websocket client, server and console for node.js.

Affected versions of this package are vulnerable to Denial of Service (DoS) when the number of received headers exceed the server.maxHeadersCount or request.maxHeadersCount threshold.

Workaround

This issue can be mitigating by following these steps:

  1. Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent.

  2. Set server.maxHeadersCount to 0 so that no limit is applied.

PoC


const http = require('http');
const WebSocket = require('ws');

const server = http.createServer();

const wss = new WebSocket.Server({ server });

server.listen(function () {
  const chars = "!#$%&'*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~".split('');
  const headers = {};
  let count = 0;

  for (let i = 0; i < chars.length; i++) {
    if (count === 2000) break;

    for (let j = 0; j < chars.length; j++) {
      const key = chars[i] + chars[j];
      headers[key] = 'x';

      if (++count === 2000) break;
    }
  }

  headers.Connection = 'Upgrade';
  headers.Upgrade = 'websocket';
  headers['Sec-WebSocket-Key'] = 'dGhlIHNhbXBsZSBub25jZQ==';
  headers['Sec-WebSocket-Version'] = '13';

  const request = http.request({
    headers: headers,
    host: '127.0.0.1',
    port: server.address().port
  });

  request.end();
});

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade ws to version 5.2.4, 6.2.3, 7.5.10, 8.17.1 or higher.

References

high severity

Code Injection

  • Vulnerable module: lodash.template
  • Introduced through: @salesforce/command@3.1.3

Detailed paths

  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/command@3.1.3 @oclif/plugin-help@2.2.3 lodash.template@4.5.0

Overview

lodash.template is a The Lodash method _.template exported as a Node.js module.

Affected versions of this package are vulnerable to Code Injection via template.

PoC

var _ = require('lodash');

_.template('', { variable: '){console.log(process.env)}; with(obj' })()

Remediation

There is no fixed version for lodash.template.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: jsonwebtoken
  • Introduced through: @salesforce/core@2.37.1 and @salesforce/command@3.1.3

Detailed paths

  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/core@2.37.1 jsonwebtoken@8.5.0
    Remediation: Upgrade to @salesforce/core@3.32.12.
  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/command@3.1.3 @salesforce/core@2.37.1 jsonwebtoken@8.5.0
    Remediation: Upgrade to @salesforce/command@5.0.0.

Overview

jsonwebtoken is a JSON Web Token implementation (symmetric and asymmetric)

Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm such that the library can be misconfigured to use legacy, insecure key types for signature verification. For example, DSA keys could be used with the RS256 algorithm.

Exploitability

Users are affected when using an algorithm and a key type other than the combinations mentioned below:

EC: ES256, ES384, ES512

RSA: RS256, RS384, RS512, PS256, PS384, PS512

RSA-PSS: PS256, PS384, PS512

And for Elliptic Curve algorithms:

ES256: prime256v1

ES384: secp384r1

ES512: secp521r1

Workaround

Users who are unable to upgrade to the fixed version can use the allowInvalidAsymmetricKeyTypes option to true in the sign() and verify() functions to continue usage of invalid key type/algorithm combination in 9.0.0 for legacy compatibility.

Remediation

Upgrade jsonwebtoken to version 9.0.0 or higher.

References

medium severity

Improper Restriction of Security Token Assignment

  • Vulnerable module: jsonwebtoken
  • Introduced through: @salesforce/core@2.37.1 and @salesforce/command@3.1.3

Detailed paths

  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/core@2.37.1 jsonwebtoken@8.5.0
    Remediation: Upgrade to @salesforce/core@3.32.12.
  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/command@3.1.3 @salesforce/core@2.37.1 jsonwebtoken@8.5.0
    Remediation: Upgrade to @salesforce/command@5.0.0.

Overview

jsonwebtoken is a JSON Web Token implementation (symmetric and asymmetric)

Affected versions of this package are vulnerable to Improper Restriction of Security Token Assignment via the secretOrPublicKey argument due to misconfigurations of the key retrieval function jwt.verify(). Exploiting this vulnerability might result in incorrect verification of forged tokens when tokens signed with an asymmetric public key could be verified with a symmetric HS256 algorithm.

Note: This vulnerability affects your application if it supports the usage of both symmetric and asymmetric keys in jwt.verify() implementation with the same key retrieval function.

Remediation

Upgrade jsonwebtoken to version 9.0.0 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: node-fetch
  • Introduced through: puppeteer@10.4.0

Detailed paths

  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 puppeteer@10.4.0 node-fetch@2.6.1
    Remediation: Upgrade to puppeteer@13.1.2.

Overview

node-fetch is a light-weight module that brings window.fetch to node.js

Affected versions of this package are vulnerable to Information Exposure when fetching a remote url with Cookie, if it get a Location response header, it will follow that url and try to fetch that url with provided cookie. This can lead to forwarding secure headers to 3th party.

Remediation

Upgrade node-fetch to version 2.6.7, 3.1.1 or higher.

References

medium severity

Server-side Request Forgery (SSRF)

  • Vulnerable module: request
  • Introduced through: @salesforce/core@2.37.1 and @salesforce/command@3.1.3

Detailed paths

  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/core@2.37.1 jsforce@1.11.1 request@2.88.2
  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/command@3.1.3 @salesforce/core@2.37.1 jsforce@1.11.1 request@2.88.2

Overview

request is a simplified http request client.

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) due to insufficient checks in the lib/redirect.js file by allowing insecure redirects in the default configuration, via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP).

NOTE: request package has been deprecated, so a fix is not expected. See https://github.com/request/request/issues/3142.

Remediation

A fix was pushed into the master branch but not yet published.

References

medium severity

Prototype Pollution

  • Vulnerable module: tough-cookie
  • Introduced through: @salesforce/core@2.37.1 and @salesforce/command@3.1.3

Detailed paths

  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/core@2.37.1 jsforce@1.11.1 request@2.88.2 tough-cookie@2.5.0
  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/command@3.1.3 @salesforce/core@2.37.1 jsforce@1.11.1 request@2.88.2 tough-cookie@2.5.0

Overview

tough-cookie is a RFC6265 Cookies and CookieJar module for Node.js.

Affected versions of this package are vulnerable to Prototype Pollution due to improper handling of Cookies when using CookieJar in rejectPublicSuffixes=false mode. Due to an issue with the manner in which the objects are initialized, an attacker can expose or modify a limited amount of property information on those objects. There is no impact to availability.

PoC

// PoC.js
async function main(){
var tough = require("tough-cookie");
var cookiejar = new tough.CookieJar(undefined,{rejectPublicSuffixes:false});
// Exploit cookie
await cookiejar.setCookie(
  "Slonser=polluted; Domain=__proto__; Path=/notauth",
  "https://__proto__/admin"
);
// normal cookie
var cookie = await cookiejar.setCookie(
  "Auth=Lol; Domain=google.com; Path=/notauth",
  "https://google.com/"
);

//Exploit cookie
var a = {};
console.log(a["/notauth"]["Slonser"])
}
main();

Details

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.

There are two main ways in which the pollution of prototypes occurs:

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

The logic of a vulnerable recursive merge function follows the following high-level model:

merge (target, source)

  foreach property of source

    if property exists and is an object on both the target and the source

      merge(target[property], source[property])

    else

      target[property] = source[property]

When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.

Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).

lodash and Hoek are examples of libraries susceptible to recursive merge attacks.

Property definition by path

There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)

If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.

Types of attacks

There are a few methods by which Prototype Pollution can be manipulated:

Type Origin Short description
Denial of service (DoS) Client This is the most likely attack.
DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf).
The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service.
For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail.
Remote Code Execution Client Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation.
For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code.
Property Injection Client The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens.
For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges.

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

  1. Freeze the prototype— use Object.freeze (Object.prototype).

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

  4. Consider using objects without prototypes (for example, Object.create(null)), breaking the prototype chain and preventing pollution.

  5. As a best practice use Map instead of Object.

For more information on this vulnerability type:

Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018

Remediation

Upgrade tough-cookie to version 4.1.3 or higher.

References

medium severity

Improper Authentication

  • Vulnerable module: jsonwebtoken
  • Introduced through: @salesforce/core@2.37.1 and @salesforce/command@3.1.3

Detailed paths

  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/core@2.37.1 jsonwebtoken@8.5.0
    Remediation: Upgrade to @salesforce/core@3.32.12.
  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/command@3.1.3 @salesforce/core@2.37.1 jsonwebtoken@8.5.0
    Remediation: Upgrade to @salesforce/command@5.0.0.

Overview

jsonwebtoken is a JSON Web Token implementation (symmetric and asymmetric)

Affected versions of this package are vulnerable to Improper Authentication such that the lack of algorithm definition in the jwt.verify() function can lead to signature validation bypass due to defaulting to the none algorithm for signature verification.

Exploitability

Users are affected only if all of the following conditions are true for the jwt.verify() function:

  1. A token with no signature is received.

  2. No algorithms are specified.

  3. A falsy (e.g., null, false, undefined) secret or key is passed.

Remediation

Upgrade jsonwebtoken to version 9.0.0 or higher.

References

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: inflight
  • Introduced through: puppeteer@10.4.0, @salesforce/core@2.37.1 and others

Detailed paths

  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 puppeteer@10.4.0 rimraf@3.0.2 glob@7.2.3 inflight@1.0.6
  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/core@2.37.1 archiver@5.3.2 archiver-utils@2.1.0 glob@7.2.3 inflight@1.0.6
  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/core@2.37.1 @salesforce/kit@1.9.2 shx@0.3.4 shelljs@0.8.5 glob@7.2.3 inflight@1.0.6
  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/command@3.1.3 @salesforce/kit@1.9.2 shx@0.3.4 shelljs@0.8.5 glob@7.2.3 inflight@1.0.6
  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/command@3.1.3 @salesforce/core@2.37.1 archiver@5.3.2 archiver-utils@2.1.0 glob@7.2.3 inflight@1.0.6
  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/core@2.37.1 archiver@5.3.2 zip-stream@4.1.1 archiver-utils@3.0.4 glob@7.2.3 inflight@1.0.6
  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/command@3.1.3 @salesforce/core@2.37.1 @salesforce/kit@1.9.2 shx@0.3.4 shelljs@0.8.5 glob@7.2.3 inflight@1.0.6
  • Introduced through: @zdware/apto@zerkz/apto#2527708cd795b9263bd3eeeb7618dd2a546828c6 @salesforce/command@3.1.3 @salesforce/core@2.37.1 archiver@5.3.2 zip-stream@4.1.1 archiver-utils@3.0.4 glob@7.2.3 inflight@1.0.6

Overview

Affected versions of this package are vulnerable to Missing Release of Resource after Effective Lifetime via the makeres function due to improperly deleting keys from the reqs object after execution of callbacks. This behavior causes the keys to remain in the reqs object, which leads to resource exhaustion.

Exploiting this vulnerability results in crashing the node process or in the application crash.

Note: This library is not maintained, and currently, there is no fix for this issue. To overcome this vulnerability, several dependent packages have eliminated the use of this library.

To trigger the memory leak, an attacker would need to have the ability to execute or influence the asynchronous operations that use the inflight module within the application. This typically requires access to the internal workings of the server or application, which is not commonly exposed to remote users. Therefore, “Attack vector” is marked as “Local”.

PoC

const inflight = require('inflight');

function testInflight() {
  let i = 0;
  function scheduleNext() {
    let key = `key-${i++}`;
    const callback = () => {
    };
    for (let j = 0; j < 1000000; j++) {
      inflight(key, callback);
    }

    setImmediate(scheduleNext);
  }


  if (i % 100 === 0) {
    console.log(process.memoryUsage());
  }

  scheduleNext();
}

testInflight();

Remediation

There is no fixed version for inflight.

References