blitzstrike 2.4.111 → 2.4.113
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +31 -0
- package/dist/index.js +594 -233
- package/intelligence/cve-corpus.json +37023 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,37 @@ All notable changes to Blitz Strike are documented here.
|
|
|
5
5
|
The format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/).
|
|
7
7
|
|
|
8
|
+
## [2.4.113] — 2026-09-17
|
|
9
|
+
|
|
10
|
+
### Added — auto-updating nuclei CVE corpus (live-read + sync tool)
|
|
11
|
+
|
|
12
|
+
- New `src/nuclei-corpus.ts`: the CVE fingerprint corpus is now read LIVE from
|
|
13
|
+
the canonical `nuclei-templates` `http/cves/**` tree whenever it is present
|
|
14
|
+
on disk (so it auto-stays current after `nuclei -update-templates`), with the
|
|
15
|
+
bundled `cve-corpus.json` as a fallback when nuclei-templates isn't installed.
|
|
16
|
+
The parsed corpus is cached; `sync_cve_corpus` invalidates it.
|
|
17
|
+
- New `sync_cve_corpus` tool: runs `nuclei -update-templates` (best-effort),
|
|
18
|
+
reloads the corpus, and reports the fresh count + whether the source is live
|
|
19
|
+
or the bundled snapshot — call it before a large recon pass to pick up
|
|
20
|
+
newly-disclosed CVEs.
|
|
21
|
+
|
|
22
|
+
## [2.4.112] — 2026-09-17
|
|
23
|
+
|
|
24
|
+
### Added — nuclei-templates CVE corpus (watchlist 35 → 4,100+ fingerprints)
|
|
25
|
+
|
|
26
|
+
- New `intelligence/cve-corpus.json` (4,113 CVEs) derived from the canonical
|
|
27
|
+
`projectdiscovery/nuclei-templates` `http/cves/**` tree via
|
|
28
|
+
`scripts/sync-cve-corpus.py` (re-runnable after `nuclei -update-templates`).
|
|
29
|
+
Each entry carries product name + severity + EPSS + CWE + a word-boundary
|
|
30
|
+
`match` regex built from product-name tokens + fofa/shodan query keywords
|
|
31
|
+
(NOT matcher payload words, which are too generic).
|
|
32
|
+
- `watchlistCveMatches` / `live_recon` now match against the hand-curated
|
|
33
|
+
watchlist (version-precise) AND the corpus (long-tail), ranked by EPSS then
|
|
34
|
+
severity, capped at 20, with the hand-curated entry overriding the corpus for
|
|
35
|
+
the same CVE. Generic infra tokens (php/apache/mysql/powered/…) are excluded
|
|
36
|
+
so a plain PHP/HTML target yields ZERO false matches — regression-tested
|
|
37
|
+
(plain php → 0; vite/gradio/ollama/n8n → their specific CVEs).
|
|
38
|
+
|
|
8
39
|
## [2.4.111] — 2026-09-17
|
|
9
40
|
|
|
10
41
|
### Added — CVE watchlist expanded 18 → 35 (2025-2026 fingerprints)
|