Vulnerability Research
Product-Focused Vulnerability Research
We search for unknown vulnerabilities in a product or component you specify. Each finding is documented so your developers can reproduce and fix it.
What it is
Vulnerability research differs from testing for known vulnerabilities. The goal is to uncover bugs in the product's own code that have not yet been found. Research starts by mapping every point where the product receives external input. These points are examined through source code review, fuzzing, and, when needed, reverse engineering.
Scope
- Network protocol handlers, file parsers, and API endpoints
- Authentication, session, and authorization logic
- Update mechanism and signature verification
- Use of third-party libraries by the product
- Reverse engineering of the compiled release if source code is unavailable
The need
When organizations need it
- Before your product is submitted to banks or public bodies that conduct their own security review.
- When a new protocol, file format, or remote management feature is added to the product.
- When your product is entering the EU market. From 11 December 2027, the Cyber Resilience Act requires products to be made available without known exploitable vulnerabilities.
Method
How we work
-
Attack surface
We identify every point where the product receives external input and the privilege level each one operates with.
-
Prioritization
We prioritize code paths that are network-accessible and run with high privileges.
-
Deep review
We manually review these code paths and fuzz the same entry points.
-
Report and retest
We report each vulnerability with its root cause and a proposed fix, then retest after remediation.
Outcome
What you have at the end
For each vulnerability found, you receive the root cause, impact, and a proposed fix. Documented code paths show which parts of the product were reviewed and to what depth.
Frequently asked questions
How is vulnerability research different from a penetration test?
A penetration test examines a system for known vulnerability types and misconfigurations within a set timeframe. Vulnerability research goes deep into a single product's code to find bugs that are not yet known.
Do you need access to the source code?
No, but it speeds up and deepens the research. If source code cannot be shared, the compiled release is analyzed through reverse engineering.
Is a CVE ID requested for a vulnerability you find?
If the product is yours, the decision to request a CVE and publish is yours. The CVE ID is assigned by a CVE Numbering Authority (CNA) covering your product. We can support you during this process if needed.
Vulnerability Research
Other services in this area
Let's talk about this service.
Tell us briefly what you need. We will agree on the scope and timing together in the first meeting.
Schedule a Meeting