Security readout for executives and security teams
Plain-English summary
LibSass 3.4.5 can read past a heap buffer when processing crafted input. The reported outcome is remote denial of service, meaning an exposed Sass compilation path could be crashed or disrupted.
Executive priority
Prioritize if any public or customer-facing workflow compiles Sass input. For internal build-only use, treat as a dependency hygiene and availability issue rather than an emergency.
Technical view
The issue is a heap-based buffer over-read in json_mkstream() in sass_context.cpp in LibSass 3.4.5. The CVE description states crafted input can cause remote denial of service. No CVSS, CWE, affected CPEs, or fixed version are provided in the supplied bundle.
Likely exposure
Exposure is most likely where applications, build services, or APIs compile Sass/SCSS using LibSass 3.4.5, especially if user-controlled input reaches the compiler.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The stated impact is denial of service from crafted input, not confirmed code execution.
Researcher notes
Evidence is sparse: the bundle names LibSass 3.4.5 and json_mkstream(), but provides no CVSS vector, CWE mapping, patch version, or proof-of-exploit details. Avoid asserting broader product exposure without environment inventory.
Mitigation direction
- Check vendor or distribution guidance for LibSass and apply recommended updates when available.
- Avoid compiling untrusted Sass/SCSS input with LibSass 3.4.5.
- Isolate Sass compilation from public-facing application processes where possible.
- Use resource limits and restart supervision around compilation workers.
Validation and detection
- Inventory dependencies and packages for LibSass 3.4.5.
- Review application flows for user-controlled Sass/SCSS reaching LibSass.
- Check containers and build images for bundled LibSass versions.
- Look for unexplained Sass compiler crashes or availability incidents.
- Confirm whether vendor advisories identify a fixed package.
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-10687 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://bugzilla.redhat.com/show_bug.cgi?id=1466411CVE 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.