Security readout for executives and security teams
Plain-English summary
This CVE affects the npm call router used by hapi. A bug can let empty route parameters avoid validation rules. Business impact depends on whether an application relies on those validations to block unsafe or unauthorized input.
Executive priority
Address during normal vulnerability remediation, with higher priority for internet-facing services or routes where validation gates sensitive actions. No provided evidence supports emergency response for active exploitation.
Technical view
call versions 2.0.1 through 3.0.1 do not validate empty parameters correctly. The CVE maps to CWE-20 improper input validation and may allow invalid input to bypass route validation. The provided sources do not include CVSS scoring, exploit details, or confirmed exploitation.
Likely exposure
Exposure is likely limited to Node.js applications using the affected call module range, directly or through hapi-era dependencies, on routes where parameter validation has security or business logic significance.
Exploitation context
The source bundle does not show CISA KEV listing, public exploitation, or exploit maturity. Treat this as a dependency risk requiring inventory and upgrade validation, not as confirmed active exploitation.
Researcher notes
Evidence is narrow but consistent: affected range, CWE-20, and validation bypass behavior are identified. Impact must be determined per application because the sources do not describe privilege impact, data exposure, or weaponized exploit paths.
Mitigation direction
- Inventory applications using the call npm module or hapi dependency trees.
- Upgrade call to 3.0.2 or a later non-affected version where compatible.
- If direct upgrade is blocked, review vendor and framework guidance before choosing a workaround.
- Prioritize routes where validation protects authorization, object selection, or sensitive workflow decisions.
Validation and detection
- Check package manifests and lockfiles for call versions >=2.0.1 and <3.0.2.
- Confirm whether hapi dependencies pull in the affected call version transitively.
- Review route tests covering empty path or route parameters.
- Add regression tests proving empty parameters cannot bypass validation rules.
Public sources used
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-20: 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-2016-10543 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://github.com/hapijs/hapi/issues/3228CVE reference · x_refsource_MISC
- https://nodesecurity.io/advisories/121CVE reference · x_refsource_MISC
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.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.