02 Research area
Exploit development
Proving impact instead of guessing it: from a crash to a primitive, from a primitive to code execution, against real mitigations on production configurations.
01 Overview
A crash is a symptom. Exploitability is a property of the whole system: allocator behaviour, object layout, the mitigations compiled in and the ones enabled at runtime. Exploit development measures it instead of assuming it.
A deterministic proof of concept settles severity debates, gets the fix prioritised, and gives the vendor a regression test that proves the patch closes the attack, not just the symptom.
02 Scope
What we prove
- 01
Memory corruption
Heap grooming to place a victim object behind a linear overflow, use-after-free reclaim with controlled data, type confusion into fake vtables: primitives escalated to arbitrary read/write.
- 02
Logic and parser flaws
Authentication bypasses, path-normalisation and parser differentials, TOCTOU races and deserialisation gadget chains: code execution without corrupting a single byte of memory.
- 03
Exploit chains
An info leak to defeat ASLR, a write primitive to redirect control flow, a privilege escalation to leave the sandbox: medium-severity bugs assembled into a critical path.
- 04
Mitigation bypass
Exploitation under ASLR and KASLR, DEP, stack canaries, CFI and CET shadow stacks, sandboxes and seccomp filters, documenting which defence held and which did not.
03 Approach
How we work
Root cause first
Every exploit starts from the precise defect (the missing bounds check, the wrong object lifetime, the truncated integer), so the exploit and the fix target the same line.
Deterministic proofs of concept
Reliability engineered in: heap state normalised, race windows widened, leaks verified, so the PoC succeeds on every run, not one in fifty.
Production configurations
Tested against release builds with default mitigations enabled, never debug binaries, so the impact rating is what an attacker would actually get.
Controlled handling
Weaponised code stays in the lab. Vendors receive the minimum needed to reproduce the bug and verify the fix.
04 Engagements
What an engagement covers
- Exploitability assessment for a vulnerability you found, received through a bug bounty or are triaging
- A deterministic proof of concept and a write-up of the full exploitation path
- A mitigation report: which defences held, which were bypassed, and how
- Patch verification against the original exploit and its variants
05 Engage
Request an
engagement
Free for open-source products
Commission the Labs team for white-box or black-box research on a product, device or service you build or depend on: zero-day hunting, exploitability assessment or threat research. Tell us the target and we will scope the work with you.
Found a vulnerability in our products? Report it privately to security@resilientx.com · security.txt