Closed dave-augustine closed 8 months ago
This report seems like a false positive to me. The SHA256 digest in your screenshot matches that of uncap.exe
at https://github.com/susam/uncap/releases/tag/0.3.0. This EXE was compiled using the source code tagged 0.3.0
on a pristine Windows VM on Azure.
If some kind community member who understands that scanning tool well could investigate and share exactly why this tool flags this binary, it would be very helpful. From my limited investigation, it does look like this tool reports false positives:
In any case, you can always compile this executable from its source code shared in this project if you have a Windows machine and a compiler. The steps to do so are available at https://github.com/susam/uncap/tree/master/dev.
By the way, the analysis report is 3 months old (see top right corner of the page). Can you try hitting the "Reanalyze" link (top right corner of the page again) and see if it still reports this digest as a problem? I am hoping they might have fixed the false positive since then.
On hitting, it passes the checks.