> For the complete documentation index, see [llms.txt](https://research.sfoffo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://research.sfoffo.com/readme.md).

# Home

<h2 align="center">Sfoffo's Research Blog</h2>

<p align="center">Welcome to my space for documenting offensive security research.<br>Here I share vulnerability findings, write-ups, and practical insights that highlight techniques, pitfalls, and lessons learned from real-world security testing.</p>

## Latest Articles

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-terminal">:terminal:</i></td><td><strong>Beyond a Fly in the Wild</strong></td><td>Breaking down WildFly’s defenses and the alternative file upload attack paths adversaries may pursue when direct code execution isn’t possible.</td><td><a href="https://51979336-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV8PIVF29WAbxFwBnOoEK%2Fuploads%2FcZ39xePtlE6oM7ZSUgCt%2Fwildfly.png?alt=media&amp;token=7979df30-6552-4328-bd9c-9b3acaf72352">wildfly.png</a></td><td><a href="/2025-articles/beyond-a-fly-in-the-wild.md">Beyond a Fly in the Wild</a></td></tr><tr><td><i class="fa-terminal">:terminal:</i></td><td><strong>CVE-2024-42845 - Invesalius3 RCE</strong></td><td>Remote Code Execution in DICOM import due to unsafe use of eval in coordinates parsing.</td><td><a href="https://51979336-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV8PIVF29WAbxFwBnOoEK%2Fuploads%2FolgtmoF7aFZNiAmEjFVA%2Fimage.png?alt=media&amp;token=308d1412-95a1-41bb-a961-5cb68944d4f9">invesalius.png</a></td><td><a href="/2024-articles/cve-2024-42845-invesalius3-rce.md">CVE-2024-42845 - Invesalius3 RCE</a></td></tr><tr><td><i class="fa-terminal">:terminal:</i></td><td><strong>Streamlining CVE Research using GitHub</strong></td><td>Highlighting GitHub's vulnerability reporting workflow and the CVEs discovered during this process.</td><td><a href="https://51979336-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV8PIVF29WAbxFwBnOoEK%2Fuploads%2FFAkkJIH6dgGqn1ZasyME%2Fgithub-security-advisory.png?alt=media&amp;token=af706d70-182f-4189-ad31-14aa0c3fe847">github-security-advisory.png</a></td><td><a href="/2024-articles/streamlining-cve-research-using-github.md">Streamlining CVE Research using GitHub</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://research.sfoffo.com/readme.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.
