Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Heap-based Buffer Overflow DoS in Ivanti Connect Secure, Policy Secure, ZTA Gateway, and Neurons for Secure Access

IdentifiersCVE-2025-5462CWE-122· Heap-based Buffer Overflow

CVE-2025-5462 is a heap-based buffer overflow affecting Ivanti Connect Secure before 22.7R2.8 or 22.8R2, Ivanti Policy Secure before 22.7R1.5, Ivanti ZTA Gateway before 22.8R2.3-723, and Ivanti Neurons for Secure Access before 22.8R1.4. The available supporting content indicates the flaw exists in shared code across these products and is caused by insufficient bounds checking when copying user-supplied data into heap-allocated buffers exposed through network-accessible interfaces. A remote unauthenticated attacker can send specially crafted input to trigger memory corruption. Based on the provided information, the expected outcome is application crash or unexpected termination resulting in denial of service.

Share:
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.

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.

Successful exploitation allows a remote unauthenticated attacker to crash the affected service or appliance, causing denial of service. The provided content does not confirm reliable code execution; it characterizes the most likely impact as memory corruption leading to process termination or service instability on exposed Ivanti remote access and zero trust appliances.

Mitigation

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

Apply vendor patches as the primary mitigation. Where immediate patching is not possible, reduce exposure of network-accessible interfaces to untrusted networks, restrict access to management and service interfaces as much as operationally feasible, and monitor for crashes or unusual service instability. The supporting content also recommends running Ivanti’s external Integrity Checker Tool before and after applying updates and monitoring systems after patching for unusual activity.

Remediation

Patch, then assume compromise.

Upgrade affected products to fixed versions released by Ivanti. Remediated versions are Ivanti Connect Secure 22.7R2.8 or 22.8R2, Ivanti Policy Secure 22.7R1.5, Ivanti ZTA Gateway 22.8R2.3-723, and Ivanti Neurons for Secure Access 22.8R1.4. The content states fixes were deployed on 2025-08-02, and for Neurons for Secure Access cloud environments the fix was already applied with no additional customer action required.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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
IvantiConnect Secureapplication
IvantiNeurons For Secure Accessapplication
IvantiPolicy Secureapplication
IvantiZero Trust Access Gatewayapplication

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

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.
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 activity1

Community discussion across Reddit, Mastodon, and other social sources.