Software Intelligence: Version Vulnerability Intelligence Engine
Interactive Software Posture Analyzer
Section titled โInteractive Software Posture AnalyzerโEnter any software product name or common alias (e.g., Apache, Veeam, httpd, OpenSSL, LiteLLM) along with an exact version string to evaluate known applicable vulnerabilities and weaponized threat exposure:
Enter a product and exact version. Discover what threatens it โ and what matters now.
1. Product Philosophy & Doctrinal Design
Section titled โ1. Product Philosophy & Doctrinal DesignโThe Hermes Software Intelligence engine follows a non-negotiable core architectural axiom:
Use deterministic structured data to determine vulnerability applicability; use intelligence to enrich, prioritize, correlate, and explain results.
In modern cybersecurity operations, relying on a large language model (LLM) to perform version comparison and interval testing produces hallucinations, dangerous false negatives, and false alarms. Hermes separates the stack into two independent tiers:
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ DETERMINISTIC LAYER โโ CPE / Product Resolution ยท Version Range Boundaries โโ Exact Ingestion Math ยท CISA KEV Status ยท EPSS Scores โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฌโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ โผโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ INTELLIGENCE LAYER โโ Exploit Maturity ยท Root Cause Analysis ยท Attack Paths โโ Hermes Editorial Cross-Linking ยท Remediation Playbooks โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ2. Nuanced Vulnerability Status Model
Section titled โ2. Nuanced Vulnerability Status ModelโA major flaw of legacy CVE aggregators is reducing complex configuration states to a binary ยซ Vulnerable / Safe ยป judgment. Hermes strictly classifies every result into five standardized states:
| Status Identifier | Operational Meaning & Criteria |
|---|---|
Affected | The supplied version falls strictly inside the documented affected version range without requiring optional non-default modules. |
Configuration dependent | The version falls inside the affected range, but active exploitation requires specific non-default flags, compiled modules (e.g., mod_cgi), or architectural prerequisites. |
Potentially affected | The vendor advisory indicates theoretical exposure across major releases, but exact minor boundary verification remains incomplete. |
Not affected | The supplied version is strictly outside the affected boundary, or is equal to or greater than the official fixed version. |
Unknown | Insufficient structured CPE range data is available to make a deterministic decision. The system refuses to guess. |
3. Fundamental Principle: โNo Known CVEโ โ โSecureโ
Section titled โ3. Fundamental Principle: โNo Known CVEโ โ โSecureโโ4. Prioritization Matrix: CISA KEV & EPSS
Section titled โ4. Prioritization Matrix: CISA KEV & EPSSโHermes layers real-world exploitation telemetry directly over CVSS base metrics:
- CISA KEV (Known Exploited Vulnerabilities): Flags whether threat actors, ransomware syndicates (e.g., Akira, Qilin), or initial access brokers are actively weaponizing the vulnerability in production environments.
- EPSS (Exploit Prediction Scoring System): Quantifies the statistical probability (0.0% to 100.0%) that a software vulnerability will be exploited in the wild within the next 30 days.
- Hermes Deep-Dive Correlation: Whenever a vulnerability is covered by original Hermes reverse-engineering research, a direct link connects the analyzer to our comprehensive disassembly, Sigma/KQL detection rules, and incident response playbooks.
5. Version Comparison & Security Delta Engine
Section titled โ5. Version Comparison & Security Delta EngineโThe workbench features a Version Comparison Mode designed to evaluate upgrade paths (e.g., 2.4.49 $\rightarrow$ 2.4.51):
- Eliminated Vulnerabilities: Flaws active in the source version that are completely neutralized in the target release.
- Residual Risks: Vulnerabilities that persist even after upgrading, highlighting when a higher patch or secondary configuration hardening is necessary.
- Regressions: Warnings if a target version inadvertently introduces newer unpatched CVEs.
- Remediation Target Recommendation: The engine automatically analyzes available vendor patches to identify the lowest version that eliminates 100% of KEV and Critical threats.
6. Hermes Threat Score (HTS) Model
Section titled โ6. Hermes Threat Score (HTS) ModelโThe Hermes Threat Score (HTS) is a composite metric on a 0 - 100 scale that quantifies true operational exposure:
HTS = Min(100, (5 ร CVSS_max) + (15 ร EPSS_max) + (25 ร KEV_flag) + (10 ร Exploit_flag))- Base Severity (up to 50 pts): Anchored on the highest active CVSS score.
- Weaponization Probability (up to 15 pts): Derived from the maximum EPSS percentile.
- CISA KEV Weight (+25 pts): Applied immediately if any flaw is being actively exploited in the wild.
- Public Exploit Availability (+10 pts): Added when verified weaponized exploit code or PoCs exist.
7. Asset Intelligence & SBOM Support (CycloneDX & SPDX)
Section titled โ7. Asset Intelligence & SBOM Support (CycloneDX & SPDX)โThe third workbench mode introduces client-side Software Bill of Materials (SBOM) ingestion, allowing organizations to audit multi-package software inventories in seconds:
Supported Manifest Formats
Section titled โSupported Manifest Formatsโ- CycloneDX (JSON 1.4 โ 1.6): Standardized specification designed by OWASP. The parser traverses root metadata components as well as nested dependencies, extracting names, exact versions, CPE identifiers, and Package URLs (
purl). - SPDX (JSON 2.2 โ 2.3): ISO/IEC 5962 international standard. Packages are ingested from the
packagescollection, resolving security locators fromexternalRefs(cpe23Type,cpe22Type,purl).
Ingestion & Canonical Resolution Workflow
Section titled โIngestion & Canonical Resolution Workflowโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ RAW SBOM MANIFEST (CycloneDX / SPDX) โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฌโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ โผโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ CANONICAL RESOLUTION PIPELINE โโ 1. CPE Match: Identifies vendor & product identifiers โโ 2. PURL Match: Parses package namespace & ecosystem types โโ 3. Alias Resolver: Maps names via fuzzy canonical engine โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฌโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ โผโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ PARALLEL DETERMINISTIC AUDIT โโ - Concurrent retrieval of partitioned product CVE datasets โโ - Deterministic version-interval matching per component โโ - Hermes Threat Score (HTS) calculation per component โโ - Aggregate Inventory HTS & Exposure Gauge โโ - Identification of Urgent Remediation Priorities โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโAggregate Inventory Threat Score
Section titled โAggregate Inventory Threat ScoreโThe overall inventory posture reflects both peak single-component exposure and horizontal multi-component risk:
Overall_HTS = Min(100, Max(HTS_components) + Min(15, (Vulnerable_Count - 1) ร 3))- Peak Component Weight: Anchored on the highest-threat asset in the fleet.
- Cumulative Exposure Factor: Escalates the score by
+3 ptsfor each additional vulnerable dependency (capped at+15 pts), accurately distinguishing an inventory with 1 vulnerable service from an environment harboring dozens of exposed entry points. - Actionable Remediation Playbook: Components harboring active CISA KEV exploitation or Critical severity CVEs are highlighted with recommended upgrade targets and instant 1-click links to run full Hermes Security Delta evaluations.
5. Dedicated Product Intelligence Profiles
Section titled โ5. Dedicated Product Intelligence ProfilesโEvery tracked core software component features a dedicated static security profile compiling overall posture, full affected version ranges, CISA KEV status, EPSS weaponization percentiles, and validated safe remediation targets: