Bug 1115711 (CVE-2018-19219) - VUL-0: CVE-2018-19219: libsass: There is a Segmentation fault at Sass:Eval:operator in libsass3.5-stable.
Summary: VUL-0: CVE-2018-19219: libsass: There is a Segmentation fault at Sass:Eval:op...
Status: RESOLVED FIXED
Alias: CVE-2018-19219
Product: openSUSE Distribution
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Leap 15.0
Hardware: Other Other
: P3 - Medium : Major (vote)
Target Milestone: ---
Assignee: Cédric Bosdonnat
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/219084/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-13 06:55 UTC by Marcus Meissner
Modified: 2019-07-24 05:57 UTC (History)
0 users

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Meissner 2018-11-13 06:55:25 UTC
rh#1643760

In LibSass 3.5-stable, there is an illegal address access at
Sass::Eval::operator that will lead to a DoS attack.

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1643760
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-19219
Comment 1 Tomáš Chvátal 2019-07-11 11:36:01 UTC
This is automated batch bugzilla cleanup.

The openSUSE 42.3 changed to end-of-life (EOL [1]) status. As such
it is no longer maintained, which means that it will not receive any
further security or bug fix updates.
As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
openSUSE (At this moment openSUSE Leap 15.1, 15.0 and Tumbleweed) please
feel free to reopen this bug against that version (!you must update the
"Version" component in the bug fields, do not just reopen please), or
alternatively create a new ticket.

Thank you for reporting this bug and we are sorry it could not be fixed
during the lifetime of the release.

[1] https://en.opensuse.org/Lifetime
Comment 2 Marcus Meissner 2019-07-11 13:17:40 UTC
15.0 and 15.1 still unfixed
Comment 3 Marcus Meissner 2019-07-24 05:57:08 UTC
fixed in the meantime by version update.