Bug 1660397 (CVE-2018-19974, CVE-2018-19975, CVE-2018-19976) - CVE-2018-19974 CVE-2018-19975 CVE-2018-19976 yara: Multiple issues
Summary: CVE-2018-19974 CVE-2018-19975 CVE-2018-19976 yara: Multiple issues
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2018-19974, CVE-2018-19975, CVE-2018-19976
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1660398 1660399
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-18 09:32 UTC by Andrej Nemec
Modified: 2019-09-29 15:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-10 10:44:06 UTC
Embargoed:


Attachments (Terms of Use)

Description Andrej Nemec 2018-12-18 09:32:12 UTC
CVE-2018-19974

In YARA 3.8.1, bytecode in a specially crafted compiled rule can read uninitialized data from VM scratch memory in libyara/exec.c. This can allow attackers to discover addresses in the real stack (not the YARA virtual stack).

https://github.com/VirusTotal/yara/issues/999

CVE-2018-19975

In YARA 3.8.1, bytecode in a specially crafted compiled rule can read data from any arbitrary address in memory, in libyara/exec.c. Specifically, OP_COUNT can read a DWORD.

https://github.com/VirusTotal/yara/issues/999

CVE-2018-19976

In YARA 3.8.1, bytecode in a specially crafted compiled rule is exposed to information about its environment, in libyara/exec.c. This is a consequence of the design of the YARA virtual machine.

https://bnbdr.github.io/posts/extracheese/
https://github.com/bnbdr/swisscheese/
https://github.com/VirusTotal/yara/issues/999

Comment 1 Andrej Nemec 2018-12-18 09:32:24 UTC
Created yara tracking bugs for this issue:

Affects: epel-all [bug 1660399]
Affects: fedora-all [bug 1660398]

Comment 2 Product Security DevOps Team 2019-06-10 10:44:06 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.