@blamejs/exceptd-skills 0.19.20 → 0.19.22
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 +20 -0
- package/data/_indexes/_meta.json +4 -4
- package/data/cve-catalog.json +4 -4
- package/data/zeroday-lessons.json +2219 -80
- package/lib/validate-package.js +6 -3
- package/manifest.json +53 -53
- package/package.json +1 -1
- package/sbom.cdx.json +19 -19
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,25 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.19.22 — 2026-08-11
|
|
4
|
+
|
|
5
|
+
Another 38 CVEs report the controls they require, taking coverage to 991 of 1025. The set includes Citrix NetScaler, Apache ActiveMQ and RocketMQ, Adobe ColdFusion, Oracle Fusion Middleware, Zimbra, Ivanti's Cloud Services Appliance, Qlik Sense, Cisco NX-OS, and the Fortinet FortiSandbox and Trend Micro Apex One entries.
|
|
6
|
+
|
|
7
|
+
Three entries put the flaw inside the security product itself. A sandbox appliance exists so hostile content detonates somewhere other than production; an endpoint-protection console exists to control the fleet; a migration tool exists to move firewall configurations. Each is carried as tooling rather than as an asset, which is how each stays outside the inventory that would have clocked it — and the migration tool holds, in its own record, the usernames, cleartext passwords, configurations and device API keys of every firewall it has handled. The requirement puts these on the tier their contents justify rather than the tier their role suggests, and states what the upgrade does not undo: credentials that passed through the tool stay valid until they are re-issued on the devices themselves.
|
|
8
|
+
|
|
9
|
+
Where an exploit's precondition is administrative access, the administrator population is the attack surface. The endpoint-protection entry needs console access before its uninstaller module can be driven into executing commands — so the requirement raises those accounts above ordinary application administrators, reachable through a privileged-access path rather than from any workstation on the corporate segment. Recording the flaw as needing a patch and stopping there leaves the prerequisite untouched.
|
|
10
|
+
|
|
11
|
+
A second-order injection is not visible at the point it is submitted. The sandbox appliance stores a value from one feature and executes it as an operating-system command later, so a check that validates input on submission sees nothing wrong. The requirement is that the configuration-accepting endpoint neutralises the value before it can reach a command sink, and the distinguishing test exercises the stored path rather than the submission path.
|
|
12
|
+
|
|
13
|
+
## 0.19.21 — 2026-08-11
|
|
14
|
+
|
|
15
|
+
Another 39 CVEs report the controls they require, taking coverage to 953 of 1025. The set includes Jenkins, PAN-OS, Ivanti EPMM and the Cloud Services Appliance, Juniper's J-Web, Veeam Cloud Connect, Veritas Backup Exec, SolarWinds Web Help Desk, Apache OFBiz, Adobe Acrobat, and IP cameras from Reolink and NUUO.
|
|
16
|
+
|
|
17
|
+
A patch that has been superseded is not a patch. The Cobalt Strike teamserver entry records that the first fix was incomplete, so a server upgraded off the vulnerable line — and even one upgraded to that first fix — can still be exploitable. The requirement refuses to close on "upgraded", and names the running version against the release that carries the complete fix, because a remediation record keyed to the first advisory reads as done while the flaw is reachable.
|
|
18
|
+
|
|
19
|
+
Where the vulnerable component is unnamed, the inventory gap is the finding. One entry describes a flaw in an unspecified third-party component packaged inside a vendor's product — so the asset record says the product name and stops, and the component that actually carried the code execution was never tracked, scanned or held to a patch SLA by anyone. The requirement is that component inventory reach the depth at which the vulnerability actually sits, and the entry is explicit that the exploitation preceded any vendor fix: no remediation clock has force in a window where no fix exists, and pretending otherwise is how that window gets recorded as compliant.
|
|
20
|
+
|
|
21
|
+
Two release tracks moving independently are two populations. The Jenkins entry names an affected weekly-line build and an affected long-term-support build, so an estate that upgrades one line and leaves a controller on the other has not finished — completion is counted per controller, not per track. The entry also separates what the upgrade does from what it cannot: the primitive is file disclosure, an unauthenticated caller obtains at least the first lines of any file on the controller, and the upgrade closes the read without unreading what was already taken.
|
|
22
|
+
|
|
3
23
|
## 0.19.20 — 2026-08-11
|
|
4
24
|
|
|
5
25
|
Another 38 CVEs report the controls they require, taking coverage to 914 of 1025. The set includes Ivanti Connect Secure and EPMM, VMware ESXi, Exchange, SharePoint, Adobe ColdFusion and Acrobat, Juniper's J-Web interface, Zimbra, Roundcube, libwebp, the Linux netfilter entries, and Outlook's credential-leak defect.
|
package/data/_indexes/_meta.json
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schema_version": "1.1.0",
|
|
3
|
-
"generated_at": "2026-08-
|
|
3
|
+
"generated_at": "2026-08-11T19:32:39.070Z",
|
|
4
4
|
"generator": "scripts/build-indexes.js",
|
|
5
5
|
"source_count": 64,
|
|
6
6
|
"source_hashes": {
|
|
7
|
-
"manifest.json": "
|
|
7
|
+
"manifest.json": "8a272417326889968145ebc4e93c57b0db3ecaa44186188769cda934e6369763",
|
|
8
8
|
"README.md": "0fa9b167172f104810e5ee6040f11ed741217f7a51c2552a15c69d2a15a164aa",
|
|
9
9
|
"data/atlas-ttps.json": "a14089671efcb4f06dd0f82d688fe49276c1370e167e4483d76e9c0a40ef41eb",
|
|
10
10
|
"data/attack-techniques.json": "e6b9bae2be71e9b73848c1c2ca7175ac4ab0c8e153565f3c0fda3824e668c3a1",
|
|
11
|
-
"data/cve-catalog.json": "
|
|
11
|
+
"data/cve-catalog.json": "3c1089b065f070984c997a601a6abd541706dbf50b3901f2ae32d0fd4542e0c2",
|
|
12
12
|
"data/cwe-catalog.json": "7b2223f0773d2f033d72fdcbf00cba9cdfdc2dff6bfb1366c9b30144396945f6",
|
|
13
13
|
"data/d3fend-catalog.json": "9a4a356a1446d7db8be8b6684fa789802405a96cdaf769f06db4136bd07db6ac",
|
|
14
14
|
"data/dlp-controls.json": "791f6a46b19b0c0fa2f46630ac8b398afb7ec9c2f2019056828c8820fe255f19",
|
|
@@ -16,7 +16,7 @@
|
|
|
16
16
|
"data/framework-control-gaps.json": "a0a43cd0c8fff6ca753bb2c98f121922ff3de63102b7d67c86c76037e28cd553",
|
|
17
17
|
"data/global-frameworks.json": "20b18a851b3ab82e57cd159b49476d69fe544f02523398b2015189ab81c7c3f8",
|
|
18
18
|
"data/rfc-references.json": "6e9017eca910ab7e4bee85ad7c23927fd6ec766f34be7fce49ebf020cec3381a",
|
|
19
|
-
"data/zeroday-lessons.json": "
|
|
19
|
+
"data/zeroday-lessons.json": "a4f86106ba3b5a75646a923ce2fc3f09bdc17aeff8357e8513a1052c5168014e",
|
|
20
20
|
"skills/kernel-lpe-triage/skill.md": "0f79c641cef6e5f4a942eb94f43c460562bf83dfb67ae112d146c39c6b320fb0",
|
|
21
21
|
"skills/ai-attack-surface/skill.md": "c97335e14cd34bd1cd3c9d2cbd397f33569a07292b2f2f7721483575eb4459f7",
|
|
22
22
|
"skills/mcp-agent-trust/skill.md": "6195c93a6cadb213051214742890fa2bf4e39bae377a654d4195f0c90bd8b896",
|
package/data/cve-catalog.json
CHANGED
|
@@ -30757,12 +30757,12 @@
|
|
|
30757
30757
|
],
|
|
30758
30758
|
"atlas_refs": [],
|
|
30759
30759
|
"framework_control_gaps": {
|
|
30760
|
-
"NIST-800-53-SI-2": "
|
|
30761
|
-
"NIS2-Art21-vulnerability-management": "Vulnerability management
|
|
30760
|
+
"NIST-800-53-SI-2": "Flaw remediation closes on the fixed release (4.13.8 / 5.5.8), which is what remediates this CVE — but the exploit precondition is a security key compromised before the update, and SI-2 has no trigger for rotating a secret whose exposure the vulnerability reveals. The upgrade closes the injection path and leaves a key the attacker may hold still in service for everything else it protects.",
|
|
30761
|
+
"NIS2-Art21-vulnerability-management": "Vulnerability management records a CVE as open or closed, with no state for the interim measure the vendor names for installs that cannot update promptly — rotating the security key. A site running that measure is neither exposed as reported nor remediated, and standard patch-tracking cannot express the difference or carry the dated upgrade item it still owes.",
|
|
30762
30762
|
"UK-CAF-B4": "Secure-by-default secrets handling should prevent the security key from being derivable/leakable via any other vector in the first place, since this CVE is only exploitable after that precondition is met.",
|
|
30763
30763
|
"GDPR-Art32": "Security-of-processing is directly undermined when a leaked application security key enables remote code execution against a system that may process personal data.",
|
|
30764
|
-
"AU-Essential-8-Patch": "Patch-application guidance
|
|
30765
|
-
"ISO-27001-2022-A.8.24": "A.8.24 use-of-cryptography and key-management
|
|
30764
|
+
"AU-Essential-8-Patch": "Patch-application guidance measures whether the fixed release landed inside the window. It has no expression for the vendor-provided interim mitigation available to installs that cannot meet it, so a site that rotated its key while remaining below the fixed release is reported identically to one that did nothing.",
|
|
30765
|
+
"ISO-27001-2022-A.8.24": "A.8.24 use-of-cryptography and key-management governs both ends of this CVE that patching does not: the precondition, a security key derivable or leakable through some other vector, and the rotation a key suspected of exposure warrants once the fixed release is in place. The upgrade remediates the code-injection path; it does not un-disclose the key, and technical-vulnerability tracking never triggers that rotation."
|
|
30766
30766
|
},
|
|
30767
30767
|
"patch_available": true,
|
|
30768
30768
|
"patch_required_reboot": false,
|