Security readout for executives and security teams
Plain-English summary
CVE-2018-3745 affects the atob Node.js module version 2.0.3 and earlier, but only under Node.js 4.x and below according to the provided record. The issue can allocate uninitialized memory when a number is passed as input, creating a possible information exposure risk in legacy JavaScript environments.
Executive priority
Handle as a targeted legacy technology risk. It should not outrank actively exploited issues, but unsupported Node.js systems using this package deserve remediation planning because old runtimes often carry broader security debt.
Technical view
The vulnerability is mapped to CWE-125 and involves atob <=2.0.3 allocating uninitialized Buffers on Node.js 4.x and earlier when input is numeric. The provided sources do not include CVSS, a named fixed version, proof of exploitation, or detailed impact boundaries beyond the legacy runtime condition.
Likely exposure
Exposure is most likely in old applications or bundled products still using atob <=2.0.3 with Node.js 4.x or older. Modern Node.js runtimes are not identified as affected in the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. Treat this as a legacy dependency information exposure issue until vendor-specific context confirms impact.
Researcher notes
Evidence is sparse: no CVSS, no exploit status, and no fix version are provided. The key validation question is whether atob <=2.0.3 runs on Node.js 4.x or below in reachable application code or affected vendor products.
Mitigation direction
- Inventory Node.js applications for atob <=2.0.3.
- Identify any runtime still using Node.js 4.x or older.
- Check package maintainer guidance for fixed atob versions.
- Review NetApp advisory for affected product-specific remediation.
- Prioritize retirement of unsupported Node.js runtimes.
Validation and detection
- Search dependency manifests and lockfiles for atob versions.
- Confirm runtime versions for applications using atob.
- Check SBOMs and appliance advisories for bundled atob.
- Document whether numeric input can reach atob in affected code paths.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2018-3745 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://hackerone.com/reports/321686CVE reference
- https://security.netapp.com/advisory/ntap-20230622-0009/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.