01 Research area
Zero-day research
Original vulnerability research in edge appliances, enterprise software, parsers and cloud control planes: the pre-auth attack surface where a single bug is a breach.
01 Overview
A zero-day has no patch, no signature and no scanner check. Finding one means modelling the target better than its developers did: where attacker-controlled bytes enter, which invariants the code assumes, and which input breaks them.
We prioritise by blast radius: pre-authentication surfaces on internet-facing appliances, components shared across vendors through common libraries and SDKs, and multi-tenant services where one bug crosses customer boundaries.
02 Scope
Where we look
- 01
Edge appliances
SSL VPNs, firewalls, ADCs and managed file transfer: pre-auth HTTP handlers, bespoke web servers and CGI binaries running as root on embedded Linux.
- 02
Parsers and protocols
File formats, codecs, TLV and ASN.1 decoders, RPC and IPC interfaces: trusted length fields, integer truncation before allocation, state machines that accept out-of-order messages.
- 03
Web platforms and APIs
Authentication and authorisation logic, parser differentials between proxies and back ends, SSRF into cloud metadata, deserialisation sinks and server-side template injection.
- 04
Cloud and identity
Tenant isolation in control planes, OAuth and SAML flows, token audience and signature validation, and the implicit trust between SaaS integrations.
03 Approach
How we hunt
Taint-guided code review
Attacker-controlled input traced from source to sink across trust boundaries, with CodeQL and Semgrep variant queries to find every sibling of a bug class once we have one.
Patch diffing
Binary and source diffs of vendor security releases to recover the root cause of silently fixed bugs, then the variants and bypasses the fix missed.
Coverage-guided and snapshot fuzzing
Structure-aware harnesses under ASan, UBSan and MSan; snapshot fuzzing of firmware and network daemons under emulation when the real hardware is out of reach.
Reverse engineering
Firmware extraction and unpacking, decompilation of closed-source binaries, and recovery of proprietary protocols, structures and dispatch tables where there is no source.
04 Engagements
What an engagement covers
- A scoped research project on a product you ship or a technology you depend on, white-box or black-box
- Per finding: root cause, CWE, CVSS v4.0 vector, affected versions and deterministic reproduction steps
- A minimal proof of concept for every confirmed vulnerability
- Fix review: your patch retested against the original bug and its variants
- Disclosure support: CVE assignment through a CNA and coordination with upstream vendors
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