GCVE-1988-2026-0514
Vulnerability from gna-1988 – Published: 2026-11-02 08:33 – Updated: 2026-11-02 08:33| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| unknown | Defense in depth |
Affected:
unknown
|
guessed |
{
"containers": {
"cna": {
"affected": [
{
"product": "Defense in depth",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Stefan Kanthak via Fulldisclosure"
}
],
"descriptions": [
{
"lang": "en",
"value": "Hi @ll,\n\nabout 2 months ago I posted\n\u003chttps://seclists.org/fulldisclosure/2025/Dec/29\u003e\n\"Defense in depth -- the Microsoft way (part 94):\n SAFER (SRPv1 and AppLocker alias SRPv2) bypass for dummies\"\n\nHere\u0027s the continuation...\n\nAbout 23 years ago, 64-bit Windows introduced the WoW64 subsystem, which\nperforms a transpatent redirection of file system and registry accesses\nfor 32-bit applications.\nTo allow consistent appearance and behaviour of 64-bit and 32-bit variants\nof applications like the \"command processor\" which reads its settings from\nthe registry key [HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Command Processor],\nseveral branches or single keys of the split registry where joined: until\nVista via \"registry reflection\", since Windows 7 via \"shared keys\".\n\nSome applications, for example the Windows Script Host, were but lobotomized:\nthe registry keys [HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows Script Host]\nand [HKEY_LOCAL_MACHINE\\SOFTWARE\\WoW6432Node\\Microsoft\\Windows Script Host]\nare separate, NOT joined.\n\nDemonstration\n~~~~~~~~~~~~~\n\nThe article \u003chttps://technet.microsoft.com/en-us/library/ee198684.aspx\u003e\n\"Disabling Windows Script Host\" states:\n\n| To disable WSH for all users of a particular computer, create this\n| entry:\n|\n| [HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows Script Host\\Settings]\n| \"Enabled\"=dword:00000000\n\nIt but needs a second, UNDOCUMENTED entry to enforce this setting:\n\n| \"IgnoreUserSettings\"=dword:00000001\n\nWithout this entry, unprivileged users can enable WSH or exempt it from\nSAFER, either Software Restriction Policies or AppLocker:\n\n| [HKEY_CURRENT_USER\\Software\\Microsoft\\Windows Script Host\\Settings]\n| \"Enabled\"=dword:00000001\n| \"UseWINSAFER\"=dword:00000000\n\nWith the first 2 entries for the computer in place, and NO entries set for\nthe user, start a command prompt, run %SystemRoot%\\SysWoW64\\CSCRIPT.EXE or\n%SystemRoot%\\SysWoW64\\WSCRIPT.EXE without arguments and admire their help\nmessages on the console or in a dialog box: OOPS!\n\nDue to the lobotomy the same entries MUST be set in the 32-bit branch of\nthe registry too! Since the key name \\WoW6432Node\\ is an implementation\ndetail you should NEVER use, run the proper command lines:\n\nREG.EXE ADD \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows Script Hosts\\Settings\" /REG:32 /V Enabled /D 0\nREG.EXE ADD \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows Script Hosts\\Settings\" /REG:32 /V IgnoreUserSettings /D 1\n\nstay tuned, and far away from split brains\nStefan Kanthak\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"providerMetadata": {
"dateUpdated": "2026-11-02T08:33:22Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Mar/5"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Mar/5"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
},
{
"url": "https://seclists.org/fulldisclosure/2025/Dec/29"
},
{
"url": "https://technet.microsoft.com/en-us/library/ee198684.aspx"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Mar/5"
],
"discovery": "EXTERNAL"
},
"title": "Defense in depth -- the Microsoft way (part 96): yet another SAFER (SRPv1) and AppLocker (SRPv2) loophole",
"x_gcve": [
{
"recordType": "advisory",
"relationships": [],
"vulnId": "GCVE-1988-2026-0514",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Mar/5",
"automated": true,
"contentSha256": "87c88bbba18df52d04390aae9c41895f73fed8826ab8e8d74c04472c172be945",
"evidenceScore": 6,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Mar/5",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-02-23T16:36:44Z"
}
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-11-02T08:33:22Z",
"dateUpdated": "2026-11-02T08:33:22Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0514"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.