CVE-2022-37617

Prototype pollution in thlorenz browserify-shim 3.8.15, due to the k variable handling in resolve-shims.js (resolveShims function). Connected sources list this as a vulnerability in the browserify-shim package, with the issue affecting resolution logic in resolve-shims.js and enabling potential p...

CVE-2022-37617: Improperly Controlled Modification of Object Prototype Attributes

Prototype pollution vulnerability in function resolveShims in resolve-shims.js in thlorenz browserify-shim 3.8.15 via the k variable in resolve-shims.js...

CVE-2022-37617

Prototype pollution vulnerability in function resolveShims in resolve-shims.js in thlorenz browserify-shim 3.8.15 via the k variable in resolve-shims.js...

browserify-shim 安全漏洞

browserify-shim is used by thlorenz individual developers to make CommonJS incompatible files browsable. A security vulnerability exists in browserify-shim version 3.8.15, which stems from a prototype contamination vulnerability found in the resolveShims function...

CVE-2022-37617

Prototype pollution vulnerability in function resolveShims in resolve-shims.js in thlorenz browserify-shim 3.8.15 via the k variable in resolve-shims.js...

PT-2022-24029 · Thlorenz · Browserify-Shim

Name of the Vulnerable Software and Affected Versions: thlorenz browserify-shim version 3.8.15 Description: The issue is related to a prototype pollution vulnerability in the resolveShims function within the resolve-shims.js file of thlorenz browserify-shim. This vulnerability is exploited via th...

Malicious Package

Overview browserify-snap is a malicious package. The package's name is based on existing repositories, namespaces, or components used by popular companies in an effort to trick employees into downloading it, also known as 'dependency confusion'. Therefore, you're only vulnerable if this package w...

Malicious code in string_decoder-browserify (npm)

--- -= Per source details. Do not edit below this line.=- Source: ghsa-malware f6ed1ac34f647ceb002ac04afb4e97e6d9a0878df27d45531f260f0013d4f296 Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be...

Malicious code in gulp-browserify-thin (npm)

--- -= Per source details. Do not edit below this line.=- Source: ghsa-malware 6ef843cda125c2cda337af64084a57a7a79a488e977a9ec4ca912704ab2059c4 Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be...

MAL-2022-3502 Malicious code in gulp-browserify-thin (npm)

--- -= Per source details. Do not edit below this line.=- Source: ghsa-malware 6ef843cda125c2cda337af64084a57a7a79a488e977a9ec4ca912704ab2059c4 Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be...

swagger-ui-browserify (>=2.1.4-a, <=2.2.3) potentially affected by CVE-2021-20086 via jquery-bbq (1.0.0)

jquery-bbq NPM version 1.0.0 is affected by a known vulnerability. The following packages have a transitive dependency on jquery-bbq and may be impacted: - swagger-ui-browserify =2.1.4-a, =2.2.3 Source cves: CVE-2021-20086 Source advisory: OSV:GHSA-7W8J-85WM-6XFQ...

Withdrawn: Arbitrary Code Execution in static-eval

All versions of package static-eval are vulnerable to Arbitrary Code Execution using FunctionExpressions and TemplateLiterals. PoC: var evaluate = require'static-eval'; var parse = require'esprima'.parse; var src="function x return...

GHSA-8V27-2FG9-7H62 Withdrawn: Arbitrary Code Execution in static-eval

All versions of package static-eval are vulnerable to Arbitrary Code Execution using FunctionExpressions and TemplateLiterals. PoC: var evaluate = require'static-eval'; var parse = require'esprima'.parse; var src="function x return...

Malicious Package in browserift

Version 16.3.3 of browserift contained malicious code as a preinstall script. The package was a backdoor that opened a connection to a remote server and executed incoming commands on both Unix and Windows machines Recommendation Any computer that has this package installed or running should be...

brocode (>=1.0.0, <=2.0.0-pre4), browserify-lazy-server (>=0.0.0-beta.0, <=0.0.0-beta.1) +10 more potentially affected by CVE-2018-14730 via browserify-hmr (0.3.7)

browserify-hmr NPM version 0.3.7 is affected by a known vulnerability. The following packages have a transitive dependency on browserify-hmr and may be impacted: - brocode =1.0.0, =0.0.0-beta.0, =0.2.0, =3.5.0, =1.0.0, =0.0.3, =2.3.0, =0.1.0, =1.0.0, =0.1.0, =0.0.11, =0.0.13 Source cves:...

Missing Origin Validation in browserify-hmr

Versions of browserify-hmr prior to 0.4.0 are missing origin validation on the websocket server. This vulnerability allows a remote attacker to steal a developer's source code because the origin of requests to the websocket server that is used for Hot Module Replacement HMR are not validated...

GHSA-77Q4-M83Q-W76V Missing Origin Validation in browserify-hmr

Versions of browserify-hmr prior to 0.4.0 are missing origin validation on the websocket server. This vulnerability allows a remote attacker to steal a developer's source code because the origin of requests to the websocket server that is used for Hot Module Replacement HMR are not validated...

Code Sniffing

browserify-hms is vulnerable to code sniffing. The code sniffing is possible because WebSocket server for HMR Hot Module Replacement does not validate the origin of the request, allowing unauthorised users to access HMR message sent by the WebSocket server via a ws://127.0.0.1:8080/ connection fr...

CVE-2018-14730

An issue was discovered in Browserify-HMR. Attackers are able to steal developer's code because the origin of requests is not checked by the WebSocket server, which is used for HMR Hot Module Replacement. Anyone can receive the HMR message sent by the WebSocket server via a ws://127.0.0.1:3123/...

CVE-2018-14730

An issue was discovered in Browserify-HMR. Attackers are able to steal developer's code because the origin of requests is not checked by the WebSocket server, which is used for HMR Hot Module Replacement. Anyone can receive the HMR message sent by the WebSocket server via a ws://127.0.0.1:3123/...