What is the severity of CVE-2016-10211?

CVE-2016-10211 has a severity rating that indicates a denial of service risk due to use-after-free vulnerabilities.

How does CVE-2016-10211 affect YARA 3.5.0?

CVE-2016-10211 allows remote attackers to exploit YARA 3.5.0, causing a denial of service through crafted rules.

What is the nature of the vulnerability in CVE-2016-10211?

CVE-2016-10211 is characterized by a use-after-free error leading to application crashes.

Is there a fix available for CVE-2016-10211?

Updating to a newer version of YARA beyond 3.5.0 is recommended to mitigate CVE-2016-10211.

How can I verify if my YARA installation is affected by CVE-2016-10211?

Check the version of YARA installed; if it is 3.5.0, it is vulnerable to CVE-2016-10211.

Vulnerability/
CVE-2016-10211

high

7.5

CWE

416

3/4/2017

6/8/2024

CVE-2016-10211: Use After Free

First published: Mon Apr 03 2017(Updated: )

libyara/grammar.y in YARA 3.5.0 allows remote attackers to cause a denial of service (use-after-free and application crash) via a crafted rule that is mishandled in the yr_parser_lookup_loop_variable function.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
VirusTotal yara	=3.5.0

Remedy

https://github.com/VirusTotal/yara/commit/890c3f850293176c0e996a602ffa88b315f4e98f

Remedy

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-10211?
CVE-2016-10211 has a severity rating that indicates a denial of service risk due to use-after-free vulnerabilities.
How does CVE-2016-10211 affect YARA 3.5.0?
CVE-2016-10211 allows remote attackers to exploit YARA 3.5.0, causing a denial of service through crafted rules.
What is the nature of the vulnerability in CVE-2016-10211?
CVE-2016-10211 is characterized by a use-after-free error leading to application crashes.
Is there a fix available for CVE-2016-10211?
Updating to a newer version of YARA beyond 3.5.0 is recommended to mitigate CVE-2016-10211.
How can I verify if my YARA installation is affected by CVE-2016-10211?
Check the version of YARA installed; if it is 3.5.0, it is vulnerable to CVE-2016-10211.

collector/nvd-index
agent/type
agent/softwarecombine
agent/remedy
collector/mitre-cve
source/MITRE
agent/references
agent/author
agent/weakness
agent/severity
agent/last-modified-date
agent/description
agent/tags
agent/first-publish-date
agent/event
agent/source
vendor/virustotal
canonical/virustotal yara
version/virustotal yara/3.5.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2016-10211?
CVE-2016-10211 has a severity rating that indicates a denial of service risk due to use-after-free vulnerabilities.
How does CVE-2016-10211 affect YARA 3.5.0?
CVE-2016-10211 allows remote attackers to exploit YARA 3.5.0, causing a denial of service through crafted rules.
What is the nature of the vulnerability in CVE-2016-10211?
CVE-2016-10211 is characterized by a use-after-free error leading to application crashes.
Is there a fix available for CVE-2016-10211?
Updating to a newer version of YARA beyond 3.5.0 is recommended to mitigate CVE-2016-10211.
How can I verify if my YARA installation is affected by CVE-2016-10211?
Check the version of YARA installed; if it is 3.5.0, it is vulnerable to CVE-2016-10211.