Cisco ASA Remote Code Execution – Verifying CVE-2016-1287

netspi.com | vulnerability | CVE-2016-1287 | #rce | #network-pentesting | #cisco-asa | #cve-2016-1287 | #ike | #vulnerability-verification

Summary

Walks through verifying CVE-2016-1287, an unauthenticated remote code execution flaw in Cisco ASA's IKE fragment reassembly, with a Python tool that distinguishes vulnerable from patched devices.

CVE: CVE-2016-1287
Published: 2017-02-28 00:00
Collected: 2026-09-20 06:06

original ↗

← PreviousAttacking SSO: Common SAML Vulnerabilities and Ways to Find Them Next →Defeating CSRF Protections Through Expired cross-domain.xml Domains

Related coverage

vulnerability · netspi.com

Set Sail: Remote Code Execution in SailPoint IQService via Default Encryption Key

SailPoint IQService before the May 2025 update allows RCE with default settings: the RPC server uses a hard-coded key without authentication or TLS, letting attackers execute arbitrary code.

vulnerability · bishopfox.com

Master Key Included: Detecting SolarWinds ARM CVE-2026-28326

CVE-2026-28326 is an unauthenticated RCE in SolarWinds ARM where a hardcoded shared secret on TCP 55555 leads to SYSTEM-level code execution. Patch now.

High · vulnerability · github.com

WordPress Core Unauthenticated Path Traversal to LFI & RCE PoC (CVE-2026-87902)

While remote code execution depends on runtime prerequisites like PEAR, the unauthenticated LFI primitive resides directly in WordPress Core and affects all major branches from 4.7.0 through 7.1.1.

vulnerability · idnsec.com

[CVE-2026-93485] Comment2XSS: Zero-Click Pre-Auth XSS to Potential RCE in WordPress Core

An unauthenticated stored XSS (CVE-2026-93485) in WordPress core's wpautop() turns crafted comments into zero-click XSS, escalating to RCE via the admin session. Fixed in 7.1.1, backported to 4.7.36.

Critical · vulnerability · github.com

CVE-2026-60004: Gitea diffpatch Git Hook Installation Remote Code Execution Exploit PoC

When self-registration is enabled, any unauthenticated attacker can create an account and immediately achieve host-level remote code execution on self-hosted Gitea instances.

vulnerability · projectzero.google

FF Sandbox Escape (CVE-2020-12388)

By James Forshaw, Project Zero In my previous blog post I discussed an issue with the Windows Kernel’s handling of Restricted Tokens which allowed me to escape the Chrome GPU sandbox. Originally I’d planned to use Firefox for the proof-of-concept as Firefox uses the same effective sandbox level as the Chrome GPU process for its content renderers. That means a FF content RCE would give code execution in a sandbox where you could abuse the Windows Kernel Restricted Tokens issue, making it much more serious.

back