What is the severity of CVE-2018-5274?

CVE-2018-5274 has been reported to potentially cause a denial of service (BSOD), indicating a significant risk to system stability.

How do I fix CVE-2018-5274?

To mitigate CVE-2018-5274, you should update Malwarebytes to the latest version or uninstall the affected version.

What systems are affected by CVE-2018-5274?

CVE-2018-5274 specifically affects Malwarebytes Premium version 3.3.1.2183.

Is there a workaround for CVE-2018-5274?

Currently, the only effective workaround for CVE-2018-5274 is to avoid using the affected driver or to limit access to local users.

What kind of impact can CVE-2018-5274 have?

CVE-2018-5274 can lead to system crashes and may allow local users to influence system behavior, resulting in unspecified impacts.

Vulnerability/
CVE-2018-5274

high

7.8

CWE

8/1/2018

5/8/2024

CVE-2018-5274: 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 0x9C40E024. 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/0x9C40E024

Frequently Asked Questions

What is the severity of CVE-2018-5274?
CVE-2018-5274 has been reported to potentially cause a denial of service (BSOD), indicating a significant risk to system stability.
How do I fix CVE-2018-5274?
To mitigate CVE-2018-5274, you should update Malwarebytes to the latest version or uninstall the affected version.
What systems are affected by CVE-2018-5274?
CVE-2018-5274 specifically affects Malwarebytes Premium version 3.3.1.2183.
Is there a workaround for CVE-2018-5274?
Currently, the only effective workaround for CVE-2018-5274 is to avoid using the affected driver or to limit access to local users.
What kind of impact can CVE-2018-5274 have?
CVE-2018-5274 can lead to system crashes and may allow local users to influence system behavior, resulting in unspecified impacts.

agent/type
agent/author
agent/severity
agent/weakness
agent/references
agent/status
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/first-publish-date
agent/event
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.