CVE-2024-39012: strategyen · n/a
Affects strategyenSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmais-ltd/strategyenpkg:npm/ais-ltd/strategyenOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-39012 effectively, organizations should first identify all instances where the ais-ltd strategyen library version 0.4.0 is used, including transitive dependencies. Immediate steps include: 1) Monitoring the vendor or repository for official patches or updates and applying them as soon as available. 2) If patches are not yet released, implement input validation and sanitization on all data passed to the mergeObjects function to prevent prototype pollution payloads. 3) Employ runtime application self-protection (RASP) or web application firewalls (WAFs) configured to detect and block prototype pollution attack patterns. 4) Conduct thorough code reviews and static analysis to identify unsafe object merges or prototype manipulations. 5) Isolate or sandbox affected components to limit the blast radius of potential exploitation. 6) Maintain strict dependency management and consider replacing or removing the vulnerable library if feasible. 7) Enhance monitoring and logging to detect anomalous behaviors indicative of exploitation attempts. These targeted measures go beyond generic advice and address the specific nature of prototype pollution vulnerabilities.
Description
ais-ltd strategyen v0.4.0 was discovered to contain a prototype pollution via the function mergeObjects. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.