Home/CVE/hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulner
CVE
CVE-2018-372811
hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulner
hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via 'merge' and 'applyToDefaults' functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects.
HIGH · CVSS 8.8
EPSS 0.04226
EPSS exploitation odds4.23% · top 10%
Act now
- Public exploit or PoC is available
- CVSS base score ≥ 7.0
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2018-3728, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
EPSS exploitation probability
4.23%
Top 10%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLifecycle
- 30 Mar 2018Published to NVD
- 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
⚠
Public Exploits & PoCs
11These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users mark whether it works, rate 1-10, and can report malware with a required reason that becomes a public comment.
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
◆
ATT&CK techniques
1Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
5Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-384 · Application API Message Manipulation via Man-in-the-Middle CAPEC-CAPEC-385 · Transaction or Event Tampering via Application API Manipulation CAPEC-CAPEC-386 · Application API Navigation Remapping CAPEC-CAPEC-387 · Navigation Remapping To Propagate Malicious Content CAPEC-CAPEC-388 · Application API Button Hijacking
⬡
Weakness Classification
▤
Affected Products & Versions
2hapijs hoek< 4.2.0
hapijs hoek>= 5.0.0 and < 5.0.3
▤
Affected Packages
1Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
npm
hoek
HIGH
fixed in 5.0.3
▤
Related CVEs
5CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.
CVE-2018-3719
mixin-deep node module before 1.3.1 suffers from a Modification of Assumed-Immut...
same CWE-471
HIGH
CVE-2018-3720
assign-deep node module before 0.4.7 suffers from a Modification of Assumed-Immu...
same CWE-471
HIGH
CVE-2018-3721
lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutabl...
same CWE-471
MEDIUM
CVE-2018-3722
merge-deep node module before 3.0.1 suffers from a Modification of Assumed-Immut...
same CWE-471
HIGH
CVE-2020-36604
hoek before 8.5.1 and 9.x before 9.0.3 allows prototype poisoning in the clone f...
same product
HIGH
⚑
Vendor Advisories
3🔗
References & Sources
3Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.