Menu

Star on GitHub · 3.2k

CVE-2020-25533

7.0 · HIGH

An issue was discovered in Malwarebytes before 4.0 on macOS.

Published Jan 15, 2021CWE-362EPSS 0.27%

Overview

CVE-2020-25533 is a high-severity vulnerability. It was published on January 15, 2021 and has a CVSS 3.1 base score of 7.0 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.0, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

An issue was discovered in Malwarebytes before 4.0 on macOS. A malicious application was able to perform a privileged action within the Malwarebytes launch daemon. The privileged service improperly validated XPC connections by relying on the PID instead of the audit token. An attacker can construct a situation where the same PID is used for running two different programs at different times, by leveraging a race condition during crafted use of posix_spawn.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2020-25533?

CVE-2020-25533 is a high-severity vulnerability. It was published on January 15, 2021 and has a CVSS 3.1 base score of 7.0 (HIGH).

How severe is CVE-2020-25533?

This vulnerability has a CVSS 3.1 base score of 7.0, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2020-25533?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2020-25533?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2020-25533 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2020

View all