YARA 3.5.0 Regexp libyara/re.c yr_re_emit Rule recursion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in YARA 3.5.0. The impacted element is the function yr_re_emit of the file libyara/re.c of the component Regexp. This manipulation as part of Rule causes denial of service.
This vulnerability is tracked as CVE-2017-9438. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in YARA 3.5.0. It has been declared as problematic. Affected by this vulnerability is the function yr_re_emit of the file libyara/re.c of the component Regexp. The manipulation as part of a Rule leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-674. The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack. As an impact it is known to affect availability. The summary by CVE is:
libyara/re.c in the regexp module in YARA 3.5.0 allows remote attackers to cause a denial of service (stack consumption) via a crafted rule (involving hex strings) that is mishandled in the _yr_re_emit function, a different vulnerability than CVE-2017-9304.
The bug was discovered 06/05/2017. The weakness was disclosed 06/05/2017 (GitHub Repository). The advisory is shared at github.com. This vulnerability is known as CVE-2017-9438. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.2
VulDB Base Score: 5.3
VulDB Temp Score: 4.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: RecursionCWE: CWE-674 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
06/05/2017 🔍06/05/2017 🔍
06/05/2017 🔍
06/05/2017 🔍
06/06/2017 🔍
12/07/2022 🔍
Sources
Advisory: 10e8bd3071677dd1fa76beeef4bc2fc427cea5e7Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-9438 (🔍)
GCVE (CVE): GCVE-0-2017-9438
GCVE (VulDB): GCVE-100-101977
Entry
Created: 06/06/2017 08:55Updated: 12/07/2022 19:05
Changes: 06/06/2017 08:55 (57), 10/13/2019 18:21 (2), 12/07/2022 18:58 (5), 12/07/2022 19:05 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.