> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/triage-and-remediation/exploit-reproduction/reading-a-reproduction.md). # Reading a Reproduction What each reproduction result means and how to read the evidence behind it. Open a vulnerability report from **Triage > Vulnerability reports**, or an eligible SAST or SCA finding, and select the **Reproduction** tab. Every section links back to raw evidence, so you can check each conclusion yourself. ## Reproduction results | Reproduction result | Shown as | Meaning | | ------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Exploitable** | Reproduced | The exploit fired in the sandbox and its impact was observed. | | **Not exploitable** | Not Exploitable | Konvu gathered evidence that the vulnerability is not present, or the report's claims do not match the code. | | **Hardening** | Hardening | The weakness is real in the code, but a mitigation stops it from being exploited at runtime. Worth fixing, at a lower priority than an exploitable finding. | | **Inconclusive** | Inconclusive | The sandbox could not reach a reproduction result, usually because of an environment limitation. It does not mean the finding is safe. | {% hint style="info" %} The report list labels a Not exploitable reproduction result **False positive**. Both labels mean the same reproduction result. {% endhint %} A run can also end without a reproduction result: * **Failed**: the run crashed before reaching a reproduction result. Run it again. * **Stopped**: the run was halted, for example after a prompt injection was detected. See [How Reproduction Works](/konvu/triage-and-remediation/exploit-reproduction/how-reproduction-works.md#reports-are-untrusted-input). ## The result banner The banner at the top gives the reproduction result in one sentence, with Konvu's confidence and the CVSS score of the vulnerability as reproduced. ## What was proven The claims Konvu tested, each marked **proven**, **disproven**, or **inconclusive**. The reproduction result is computed from this list (see [How Reproduction Works](/konvu/triage-and-remediation/exploit-reproduction/how-reproduction-works.md#how-the-reproduction-result-is-computed)), so this is the place to start when you disagree with a reproduction result. ## Reproduction run Expand **Environment** and **Execution** to see how the sandbox was built and what the attacker did. **Environment** * **Target**: the application and version that were deployed. * **Attacker position**: where the attacker started, such as unauthenticated from the internet or a logged-in user. * **Checked out**: the exact commit or version built. * **Smoke test**: whether the application was confirmed healthy before the attack. * **See hosts and services**: a map of the sandbox's hosts and how the attacker reached the target. * **Where the lab differs from production**: settings, services, or data that the sandbox could not match. Check this list before relying on a reproduction result. **Execution** The steps the attacker agent took, with the evidence for each: * **Request / Response**: the HTTP requests sent and what came back, headers included. * **Script / Output**: commands and scripts run, with their output. * **Console messages**: browser console output, for client-side exploits. ## Chain and blast radius **Chain** describes how the attacker got from their starting position to the vulnerable code. **Blast radius** describes what they could reach once there: data, accounts, or systems. ## Disproof investigation When the exploit does not fire, the disproof investigation explains what Konvu checked to rule the vulnerability out: code paths that do not exist, input that is validated, or a mitigation that blocks the attack. Read it before closing a report as Not exploitable. ## Remediation The **Remediation** tab carries Konvu's fix recommendations. When the vulnerability is reproduced, **Copy remediation prompt** copies a prompt for your coding agent with the vulnerability, the proof, and the recommendations. Konvu does not open fix pull requests for vulnerability reports. See [Vulnerability Reports](/konvu/triage-and-remediation/finding-types/vulnerability-reports.md#act-on-the-results). ## Share a result Every report and finding has its own URL. Link it from a ticket or a bug bounty reply, and anyone in your organization with access to Konvu lands on the same reproduction result. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.konvu.com/konvu/triage-and-remediation/exploit-reproduction/reading-a-reproduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.