Bug 1085789 - (CVE-2018-8754) VUL-0: CVE-2018-8754: libevt: The libevt_record_values_read_event() function does not properly check for out-of-bounds values of user SID data size, strings size, or data size.
(CVE-2018-8754)
VUL-0: CVE-2018-8754: libevt: The libevt_record_values_read_event() function ...
Status: REOPENED
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: Security
Leap 15.1
Other Other
: P3 - Medium : Normal (vote)
: ---
Assigned To: Greg Freemyer
Security Team bot
https://smash.suse.de/issue/202199/
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-03-19 06:56 UTC by Johannes Segitz
Modified: 2020-01-16 13:52 UTC (History)
2 users (show)

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 Johannes Segitz 2018-03-19 06:56:17 UTC
CVE-2018-8754

The libevt_record_values_read_event() function in libevt_record_values.c in
libevt before 2018-03-17 does not properly check for out-of-bounds values of
user SID data size, strings size, or data size.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-8754
https://github.com/libyal/libevt/commit/444ca3ce7853538c577e0ec3f6146d2d65780734
Comment 1 Tomáš Chvátal 2019-07-11 11:28:28 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 14:58:45 UTC
15.0 and 15.1 still seem to have the affected versiuon.