<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>tools on naved // security notes</title><link>https://naved124.github.io/tags/tools/</link><description>Recent content in tools on naved // security notes</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 04 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://naved124.github.io/tags/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>reconforge v0.3: why keyword CVE matching lies</title><link>https://naved124.github.io/notes/reconforge-v0-3/</link><pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate><guid>https://naved124.github.io/notes/reconforge-v0-3/</guid><description>Replacing a keyword CVE search with CPE matching, local version checks and a confidence level on every result. Most of the work turned out to be NVD&amp;rsquo;s data, not the API.</description></item><item><title>building reconforge: recon that writes the report for you</title><link>https://naved124.github.io/notes/building-reconforge/</link><pubDate>Fri, 30 Oct 2026 00:00:00 +0000</pubDate><guid>https://naved124.github.io/notes/building-reconforge/</guid><description>&lt;h2 id="the-idea-in-one-paragraph"&gt;The idea in one paragraph&lt;/h2&gt;&#10;&lt;p&gt;Every box and every engagement starts the same way: scan, read the Nmap output, google each&#10;service version for CVEs, check whether Metasploit has a module, then write it all down.&#10;&lt;a href="https://github.com/Naved124/reconforge"&gt;reconforge&lt;/a&gt; automates that first hour. It takes a&#10;target, refuses to touch it unless it&amp;rsquo;s in an authorized scope file, runs Nmap, and turns the&#10;output into a Markdown report: misconfigurations first, candidate CVEs second, Metasploit&#10;modules third, next steps at the end. It doesn&amp;rsquo;t exploit anything. It hands a human a&#10;prioritised list to verify.&lt;/p&gt;</description></item></channel></rss>