Vulnerabilities

3 via 4 paths

Dependencies

514

Source

GitHub

Commit

b8e6d31c

Find, fix and prevent vulnerabilities in your code.

Issue type
  • 3
  • 1
Severity
  • 3
  • 1
Status
  • 4
  • 0
  • 0

medium severity
new

Use of a Cryptographic Primitive with a Risky Implementation

  • Vulnerable module: elliptic
  • Introduced through: powerbi-visuals-tools@5.6.0

Detailed paths

  • Introduced through: @microsoft/powerbi-visuals-chordchart@Microsoft/powerbi-visuals-chord#b8e6d31c89956320a92c6dd23d56a3796a453f5a powerbi-visuals-tools@5.6.0 crypto-browserify@3.12.1 browserify-sign@4.2.5 elliptic@6.6.1
  • Introduced through: @microsoft/powerbi-visuals-chordchart@Microsoft/powerbi-visuals-chord#b8e6d31c89956320a92c6dd23d56a3796a453f5a powerbi-visuals-tools@5.6.0 crypto-browserify@3.12.1 create-ecdh@4.0.4 elliptic@6.6.1

Overview

elliptic is a fast elliptic-curve cryptography implementation in plain javascript.

Affected versions of this package are vulnerable to Use of a Cryptographic Primitive with a Risky Implementation due to the incorrect computation of the byte-length of k value with leading zeros resulting in its truncation. An attacker can obtain the secret key by analyzing both a faulty signature generated by a vulnerable implementation and a correct signature for the same inputs.

Note:

There is a distinct but related issue CVE-2024-48948.

Remediation

There is no fixed version for elliptic.

References

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: inflight
  • Introduced through: powerbi-visuals-tools@5.6.0

Detailed paths

  • Introduced through: @microsoft/powerbi-visuals-chordchart@Microsoft/powerbi-visuals-chord#b8e6d31c89956320a92c6dd23d56a3796a453f5a powerbi-visuals-tools@5.6.0 extra-watch-webpack-plugin@1.0.3 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

medium severity

Artistic-2.0 license

  • Module: domain-browser
  • Introduced through: powerbi-visuals-tools@5.6.0

Detailed paths

  • Introduced through: @microsoft/powerbi-visuals-chordchart@Microsoft/powerbi-visuals-chord#b8e6d31c89956320a92c6dd23d56a3796a453f5a powerbi-visuals-tools@5.6.0 domain-browser@5.7.0

Artistic-2.0 license

low severity

Directory Traversal

  • Vulnerable module: sirv
  • Introduced through: powerbi-visuals-tools@5.6.0

Detailed paths

  • Introduced through: @microsoft/powerbi-visuals-chordchart@Microsoft/powerbi-visuals-chord#b8e6d31c89956320a92c6dd23d56a3796a453f5a powerbi-visuals-tools@5.6.0 webpack-bundle-analyzer@4.10.2 sirv@2.0.4

Overview

sirv is a The optimized & lightweight middleware for serving requests to static assets

Affected versions of this package are vulnerable to Directory Traversal via the viaLocal function, which uses a dirname prefix. An attacker can access files outside the intended public directory by sending crafted requests that exploit symlinks and naming similarities, bypassing access restrictions.

Note: This is only exploitable if the server is explicitly exposed to the network using the --host flag or the server.host configuration option, the public directory feature is enabled, and there are symlinks in a public 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 sirv to version 3.0.2 or higher.

References