← ClaudeAtlas

defend-memory-corruptionlisted

Compiler and allocator hardening against memory-corruption exploitation - stack and heap buffer overflows, use-after-free, and integer overflows that attackers turn into code execution (MITRE ATT&CK T1203, T1068, T1210; D3FEND D3-PSEP, D3-SAOR, D3-SFCV, D3-SSC, D3-EHPV). Signals live in the Windows Application log (Event ID 1000, exception codes 0xc0000409, 0xc0000374, 0xc0000005), the Security-Mitigations channels, Sysmon process-creation events, and Linux journald/auditd segfault and glibc abort messages. Gives which hardening flags and allocator settings to deploy, how to verify posture across a fleet, and how to spot failed exploit attempts in crash telemetry. Use when hardening C or C++ builds, choosing GCC/Clang or MSVC security flags, enabling DEP/ASLR/CFG/CET or a hardened allocator, auditing exploit-protection posture, triaging repeated crashes on an internet-facing service, or hunting memory-corruption exploitation.
umbrasec-labs/umbra-blue · ★ 0 · AI & Automation · score 62
Install: claude install-skill umbrasec-labs/umbra-blue
# Memory-Corruption Exploitation - Defensive Methodology > **Tier 2 - methodology skill.** No bespoke UMBRASEC detection rule ships with this skill yet. It gives the defender's method, the log sources and signals, and the hardening, and points to public rule sources. Promotion to Tier 1 (a sourced, tuned UMBRASEC rule) is tracked in [COVERAGE.md](https://github.com/umbrasec-labs/umbra-blue/blob/main/COVERAGE.md). Do not treat the content below as citing a UMBRASEC rule; there is none for this threat yet. ## TL;DR for defenders Memory corruption (stack and heap overflows, use-after-free, integer overflow) is the raw material of most binary exploitation. You cannot patch the whole class away, but every mitigation you turn on forces the attacker to chain more primitives, and each extra step is another chance to crash and get caught. Do three things: build first-party C and C++ with the full hardening flag set, enforce OS-level exploit protection (DEP, ASLR, CFG, CET, SafeSEH) across the fleet, and collect the crash and mitigation telemetry so a failed exploit attempt shows up as an alert instead of a silently restarted service. This skill is defensive: it explains exploitation only as far as hardening and detection need, and ships no exploit tooling. ## What it looks like, defender view A real exploit attempt that fails against your mitigations does not look like malware; it looks like a crash. The hardening above converts a quiet memory overwrite into a loud, specific proc