artkamote / examples

Serverless Examples – A collection of boilerplates and examples of serverless architectures built with the Serverless Framework on AWS Lambda, Microsoft Azure, Google Cloud Functions, and more.
https://www.serverless.com/examples/
Other
0 stars 0 forks source link

CVE-2023-46234 (Medium) detected in browserify-sign-4.0.4.tgz, browserify-sign-4.2.1.tgz #331

Open mend-bolt-for-github[bot] opened 11 months ago

mend-bolt-for-github[bot] commented 11 months ago

CVE-2023-46234 - Medium Severity Vulnerability

Vulnerable Libraries - browserify-sign-4.0.4.tgz, browserify-sign-4.2.1.tgz

browserify-sign-4.0.4.tgz

adds node crypto signing for browsers

Library home page: https://registry.npmjs.org/browserify-sign/-/browserify-sign-4.0.4.tgz

Path to dependency file: /aws-node-oauth-dropbox-api/package.json

Path to vulnerable library: /aws-node-oauth-dropbox-api/node_modules/browserify-sign/package.json,/aws-node-typescript-kinesis/node_modules/browserify-sign/package.json,/aws-node-typescript-sqs-standard/node_modules/browserify-sign/package.json,/aws-node-fullstack/frontend/node_modules/browserify-sign/package.json,/aws-node-github-check/node_modules/browserify-sign/package.json,/aws-node-typescript-nest/node_modules/browserify-sign/package.json

Dependency Hierarchy: - webpack-4.41.2.tgz (Root Library) - node-libs-browser-2.2.1.tgz - crypto-browserify-3.12.0.tgz - :x: **browserify-sign-4.0.4.tgz** (Vulnerable Library)

browserify-sign-4.2.1.tgz

adds node crypto signing for browsers

Library home page: https://registry.npmjs.org/browserify-sign/-/browserify-sign-4.2.1.tgz

Path to dependency file: /azure-node-typescript-servicebus-trigger-endpoint/package.json

Path to vulnerable library: /azure-node-typescript-servicebus-trigger-endpoint/node_modules/browserify-sign/package.json,/aws-node-vue-nuxt-ssr/node_modules/browserify-sign/package.json,/azure-node-line-bot/node_modules/browserify-sign/package.json,/aws-node-signed-uploads/node_modules/browserify-sign/package.json,/azure-node-telegram-bot/node_modules/browserify-sign/package.json,/aws-node-dynamic-image-resizer/node_modules/browserify-sign/package.json

Dependency Hierarchy: - nuxt-2.15.8.tgz (Root Library) - webpack-2.15.8.tgz - webpack-4.46.0.tgz - node-libs-browser-2.2.1.tgz - crypto-browserify-3.12.0.tgz - :x: **browserify-sign-4.2.1.tgz** (Vulnerable Library)

Found in HEAD commit: dcbe4aefe4b3685f4b15493a01db0f19b118a0c4

Found in base branch: master

Vulnerability Details

browserify-sign is a package to duplicate the functionality of node's crypto public key functions, much of this is based on Fedor Indutny's work on indutny/tls.js. An upper bound check issue in `dsaVerify` function allows an attacker to construct signatures that can be successfully verified by any public key, thus leading to a signature forgery attack. All places in this project that involve DSA verification of user-input signatures will be affected by this vulnerability. This issue has been patched in version 4.2.2.

Publish Date: 2023-10-26

URL: CVE-2023-46234

CVSS 3 Score Details (6.5)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/browserify/browserify-sign/security/advisories/GHSA-x9w5-v3q2-3rhw

Release Date: 2023-10-26

Fix Resolution (browserify-sign): 4.2.2

Direct dependency fix Resolution (webpack): 4.41.3

Fix Resolution (browserify-sign): 4.2.2

Direct dependency fix Resolution (nuxt): 2.16.0


Step up your Open Source Security Game with Mend here

mend-bolt-for-github[bot] commented 3 months ago

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

mend-bolt-for-github[bot] commented 3 months ago

:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.