{"id":"CVE-2017-11554","url":"https://www.cyber-defence.io/tools/cve/CVE-2017-11554","generatedAt":"2026-10-28T21:55:12.934Z","title":"There is a stack consumption vulnerability in the lex function in parser.hpp (as used in sassc) in LibSass 3.4.5.","description":"There is a stack consumption vulnerability in the lex function in parser.hpp (as used in sassc) in LibSass 3.4.5. A crafted input will lead to a remote denial of service.","published":"2017-07-23T03:29:01.000Z","lastModified":"2026-06-17T01:02:00.000Z","status":"Modified","sourceIdentifier":"cve@mitre.org","cvss":{"version":"3.0","score":7.5,"severity":"HIGH","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"},"cwe":["CWE-674"],"affected":["libsass/libsass"],"epss":{"score":0.01879,"percentile":0.79323,"date":"2026-10-27","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (1.88%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1471780","tags":["Exploit","Issue Tracking","Third Party Advisory"],"source":"cve@mitre.org"},{"url":"https://github.com/sass/libsass/issues/2445","tags":["Third Party Advisory"],"source":"cve@mitre.org"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1471780","tags":["Exploit","Issue Tracking","Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://github.com/sass/libsass/issues/2445","tags":["Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2017-11554","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}