Security readout for executives and security teams
Plain-English summary
Older Mapbox.js versions could allow cross-site scripting in uncommon configurations involving TileJSON map names and the map share control. If exposed, an attacker may cause script to run in a user's browser within the affected site context. The source bundle does not provide CVSS, CWE, or active exploitation evidence.
Executive priority
Treat this as a cleanup priority for legacy web assets. Urgency rises if the affected library is internet-facing, used on authenticated pages, or receives map metadata from third parties.
Technical view
CVE-2017-1000043 affects Mapbox.js 1.x before 1.6.6 and 2.x before 2.2.4. The reported weakness is XSS via TileJSON name handling and map share control. The CVE affected product fields are incomplete, but the description names Mapbox.js and the vulnerable version ranges.
Likely exposure
Exposure is most likely in web applications still loading Mapbox.js 1.x or 2.x below the fixed versions, especially where TileJSON metadata or sharing controls are enabled and influenced by external data.
Exploitation context
The bundle marks KEV as false and provides no evidence of active exploitation. Public references include a Node Security advisory and a HackerOne report, indicating public disclosure, but not current exploitation status.
Researcher notes
Evidence is limited to the CVE description and listed public references. Validate the exact Mapbox.js artifact in production, not only package manifests, because old JavaScript may be vendored or CDN-loaded outside normal dependency tracking.
Mitigation direction
- Upgrade Mapbox.js 1.x to 1.6.6 or later.
- Upgrade Mapbox.js 2.x to 2.2.4 or later.
- Check vendor guidance before using other workarounds.
- Restrict or review externally supplied TileJSON metadata.
- Disable affected share-control usage where upgrade is delayed.
Validation and detection
- Inventory pages and bundles that load Mapbox.js.
- Confirm Mapbox.js versions are not below 1.6.6 or 2.2.4.
- Review code paths using TileJSON name metadata.
- Identify whether map share controls are enabled.
- Check dependency lockfiles and deployed static assets.
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.
CVE-2017-1000043 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://nodesecurity.io/advisories/74CVE reference · x_refsource_CONFIRM
- https://hackerone.com/reports/99245CVE 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.