GCVE-1988-2026-0572
Vulnerability from gna-1988 – Published: 2026-11-17 19:38 – Updated: 2026-11-17 19:38| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| unknown | starshield-forensics |
Affected:
unknown
|
guessed |
{
"containers": {
"cna": {
"affected": [
{
"product": "starshield-forensics",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Ziqi Xiao"
}
],
"descriptions": [
{
"lang": "en",
"value": "Tool: starshield-forensics v0.3.7 \u0026 StarShield-Bench-24\nCategory: Digital Forensics / Incident Response (DFIR) \u0026 AI Security\nLicense: MIT (Open Source, Python \u003e= 3.10 standard library only)\nAuthor: Ziqi Xiao (@Ziqi)\nRepository: https://github.com/Ziqi/starshield-forensics\nRelease Tag:\nhttps://github.com/Ziqi/starshield-forensics/releases/tag/v0.3.7\nDocumentation: https://ziqi.github.io/starshield/\nZenodo DOI: https://doi.org/10.5281/zenodo.24145804 (v0.3.7:\n10.5281/zenodo.24156262)\nSupply Chain: OpenSSF Best Practices Silver (#16602) | Scorecard 7.1/10\n https://www.bestpractices.dev/projects/16602\n\n\n1. Summary \u0026 Threat Context\n---------------------------\nDuring Business Email Compromise (BEC), supplier invoice diversion, and\nAuthorized Push Payment (APP) fraud investigations, browser-based messaging\nand invoicing apps frequently propagate UI retractions or post-transfer\nedits as soft-delete updates while uncompacted Chromium IndexedDB / Local\nStorage LevelDB write-ahead logs (.log) still retain earlier UTF-8 or\nUTF-16LE JSON records or text fragments on disk.\n\nAt the same time, piping untrusted adversary chat exports directly into LLM\nsummarizers exposes incident responders to indirect prompt injection (OWASP\nLLM01) and fabricated payment routing identifiers.\n\nstarshield-forensics v0.3.7 is a deterministic, offline Python 3.10+\nstandard-library CLI utility (zero external PyPI dependencies) packaged as\na reproducible single-file .pyz zipapp for restricted lab and triage hosts.\n\n\n2. Technical Capabilities (v0.3.7)\n----------------------------------\n- Redacted Storage Feasibility Check (`precheck`):\n Scans read-only copies of Chromium IndexedDB / Local Storage directories\n offline, distinguishing uncompacted `.log` WAL segments from Snappy\n `.ldb` SSTables (footer magic `0xdb4775248b80fb57`) and Blink `0xFF`\n envelopes (`GO` / `PARTIAL` / `NO_GO_COMPACTED_OR_UNSUPPORTED`) using\n aggregate counts only without emitting raw message plaintext or paths.\n\n- Cross-Block 32 KiB LevelDB `.log` Carver (`parse-leveldb-log`):\n Parses physical 32,768-byte WAL blocks, verifies masked Castagnoli CRC32C\n (`(((crc \u003e\u003e 15) | (crc \u003c\u003c 17)) + 0xA282EAD8) mod 2^32`), reassembles\n `FULL`, `FIRST`, `MIDDLE`, and `LAST` fragments across `0x8000` block\n boundaries, and carves soft-deleted / edited JSON records\n (`--schema auto|chatsvc|generic-json`) anchored to exact physical byte\n offsets (`leveldb_batch_byte_offset`).\n\n- Exported JSON Triage \u0026 Container Provenance (`triage-json`,\n`inspect-image`):\n Enumerates `deletetime` / `edittime` records in JSON exports and performs\n neutral structural verification of RFC 2083 PNG chunks\n(`IHDR`/`iCCP`/`IDAT`)\n and multi-segment ISO 10918 JPEG `APP2` ICC (`acsp`) + `APP13` (`8BIM`)\n markers, paired with explicit OS-screenshot caveats to prevent\noverclaiming.\n\n- Payment Identifier Checksums \u0026 Keyed Pseudonymization:\n Validates ISO/IEC 7812 Luhn card numbers, 89-country ISO-13616 IBAN\n Mod-97 checksums, intra-message UK Sort Code + 8-digit account pairs,\n and ISO-9362 SWIFT/BIC syntax (250 ISO-3166 country codes). Suppresses\n filenames, byte counts, and stderr snippets while pseudonymising matched\n identifiers by default via per-run keyed HMAC-SHA256 tokens\n (`--hmac-digest {sha256,sha384,blake2b}`).\n\n- `StarShield-Bench-24` Synthetic Evaluation Corpus:\n 24 seeded synthetic test cases (`SSB24-01`..`SSB24-24`) scoring WAL\n recovery, byte-offset citation accuracy, malformed-container rejection,\n and bilingual indirect prompt-injection resilience; paired with 12\n companion financial-triage cases (`TC-0456`..`TC-0467`) submitted\n upstream in OWASP GenAI Data Security Initiative PR #119.\n\n\n3. Reproducible Build \u0026 Cryptographic Verification\n--------------------------------------------------\nSingle-file reproducible `starshield.pyz` SHA-256 (`v0.3.7`):\n e6603ef083b20a5460bf56818f63a3a94b856deb377a5b6330be2394e0e21232\n\nMaintainer OpenSSH Ed25519 Signing Key (`KEYS.pub` in repository):\n 2196305+Ziqi () users noreply github com namespaces=\"file,git\" ssh-ed25519\nAAAAC3NzaC1lZDI1NTE5AAAAIKz9qGDNELwOsoNnmZIpLKQ+5HOqdE4ilZaTRA/1LR7a\n\nVerification commands (OpenSSH \u003e= 8.2p1, zero external packages):\n ssh-keygen -Y verify -f KEYS.pub \\\n -I \"2196305+Ziqi () users noreply github com\" \\\n -n file -s SHA256SUMS.sig \u003c SHA256SUMS\n shasum -a 256 -c SHA256SUMS\n python3 scripts/build_reproducible.py --verify\n\nBug reports, edge-case Chromium WAL test vectors, and technical critiques\nare welcome via GitHub Issues: https://github.com/Ziqi/starshield-forensics\n\n-- \nZiqi Xiao\nIndependent Security Architect \u0026 Digital Forensics Researcher\nhttps://ziqi.github.io/starshield/\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-17T19:38:26Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/39"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Nov/39"
},
{
"url": "https://doi.org/10.5281/zenodo.24145804"
},
{
"url": "https://github.com/Ziqi/starshield-forensics"
},
{
"url": "https://github.com/Ziqi/starshield-forensics/releases/tag/v0.3.7"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
},
{
"url": "https://www.bestpractices.dev/projects/16602"
},
{
"url": "https://ziqi.github.io/starshield/"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Nov/39"
],
"discovery": "EXTERNAL"
},
"title": "[Tool] starshield-forensics v0.3.7: Offline Chromium LevelDB .log carver (Python stdlib, MIT)",
"x_gcve": [
{
"recordType": "advisory",
"relationships": [],
"vulnId": "GCVE-1988-2026-0572",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Nov/39",
"automated": true,
"contentSha256": "17c82ad41f2950f99b6600b86e5445cff587fe6e559e6443a1c8ab84f40196e4",
"evidenceScore": 7,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Nov/39",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-11-13T03:12:19Z"
}
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-11-17T19:38:26Z",
"dateUpdated": "2026-11-17T19:38:26Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0572"
},
"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.