What is the severity of CVE-2018-5276?

CVE-2018-5276 is considered to potentially cause a denial of service, specifically a BSOD, on affected systems.

How do I fix CVE-2018-5276?

To address CVE-2018-5276, users should update Malwarebytes Premium to the latest version as provided by the vendor.

What impact does CVE-2018-5276 have on affected systems?

CVE-2018-5276 allows local users to cause a denial of service or possibly other unspecified impacts.

Which versions of Malwarebytes are affected by CVE-2018-5276?

Malwarebytes Premium version 3.3.1.2183 is specifically identified as affected by CVE-2018-5276.

Is there a workaround for CVE-2018-5276?

There are no specific workarounds for CVE-2018-5276 other than updating the software to mitigate the vulnerability.

Vulnerability/
CVE-2018-5276

high

7.8

CWE

8/1/2018

5/8/2024

CVE-2018-5276: Input Validation

First published: Mon Jan 08 2018(Updated: )

** DISPUTED ** In Malwarebytes Premium 3.3.1.2183, the driver file (FARFLT.SYS) allows local users to cause a denial of service (BSOD) or possibly have unspecified other impact because of not validating input values from IOCtl 0x9c40e018. NOTE: the vendor reported that they "have not been able to reproduce the issue on any Windows operating system version (32-bit or 64-bit)."

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Malwarebytes Anti-Malware	=3.3.1.2183

Never miss a vulnerability like this again

Reference Links

https://github.com/ZhiyuanWang-Chengdu-Qihoo360/Malwarebytes_POC/tree/master/0x9c40e018

Frequently Asked Questions

What is the severity of CVE-2018-5276?
CVE-2018-5276 is considered to potentially cause a denial of service, specifically a BSOD, on affected systems.
How do I fix CVE-2018-5276?
To address CVE-2018-5276, users should update Malwarebytes Premium to the latest version as provided by the vendor.
What impact does CVE-2018-5276 have on affected systems?
CVE-2018-5276 allows local users to cause a denial of service or possibly other unspecified impacts.
Which versions of Malwarebytes are affected by CVE-2018-5276?
Malwarebytes Premium version 3.3.1.2183 is specifically identified as affected by CVE-2018-5276.
Is there a workaround for CVE-2018-5276?
There are no specific workarounds for CVE-2018-5276 other than updating the software to mitigate the vulnerability.

agent/type
agent/severity
agent/weakness
agent/references
agent/author
agent/status
agent/softwarecombine
agent/description
agent/first-publish-date
agent/event
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-api
source/NVD
agent/software-canonical-lookup
status/disputed
vendor/malwarebytes
canonical/malwarebytes anti-malware
version/malwarebytes anti-malware/3.3.1.2183

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.