LowPublic exploit

Arbitrary Kernel Memory Read in Fortinet FortiClient Drivers

IdentifiersCVE-2015-4077CWE-200· Exposure of Sensitive Information…

A vulnerability in the mdare64_48.sys, mdare32_48.sys, mdare32_52.sys, and mdare64_52.sys drivers in Fortinet FortiClient before version 5.2.4 allows local users to read arbitrary kernel memory by issuing a specially crafted 0x22608C ioctl call. This flaw exposes sensitive kernel memory to unprivileged users, potentially leaking critical information.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Local attackers can exploit this vulnerability to read arbitrary kernel memory, which may lead to the disclosure of sensitive information such as kernel pointers, credentials, or other data that could facilitate further attacks such as privilege escalation or bypassing security mechanisms.

Mitigation

If you can’t patch tonight, do this now.

Restrict local access to systems running vulnerable versions of FortiClient, and ensure that only trusted users have local access until the software is updated. Consider monitoring for suspicious use of the vulnerable ioctl call as a temporary measure.

Remediation

Patch, then assume compromise.

Upgrade Fortinet FortiClient to version 5.2.4 or later, where this vulnerability has been addressed and the affected drivers have been patched to prevent arbitrary kernel memory reads via the ioctl interface.

PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).

VALID 1 / 2 TOTALView more in app

forti_shieldMaturityOperationalVerified exploit

This repository contains a local privilege escalation exploit targeting Windows 10 20H2, specifically leveraging CVE-2021-31955, CVE-2015-4077, and CVE-2015-5736. The main exploit logic resides in 'forti_exploit.cpp', which orchestrates the attack by leaking kernel addresses, manipulating kernel memory, and ultimately stealing the SYSTEM token using custom shellcode found in 'token_stealing.asm'. The exploit is operational but not weaponized, as it relies on hardcoded offsets and is not version-independent. The exploit launches a SYSTEM-level command shell upon success. The repository includes standard C++ project files and headers, with the main entry point in 'forti_exploit.cpp'. No network endpoints are involved; the attack vector is purely local, requiring code execution on the target machine. The exploit manipulates specific files in the user's AppData directory as part of its process.

ApexPredator-InfoSecDisclosed Oct 29, 2025cppassemblylocal

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

FortinetForticlientapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity