GCVE-1988-2026-0471
Vulnerability from gna-1988 – Published: 2026-11-02 07:30 – Updated: 2026-11-02 07:30| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| unknown | StreamSets Transformer |
Affected:
unknown
|
guessed |
{
"containers": {
"cna": {
"affected": [
{
"product": "StreamSets Transformer",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "disclosure via Fulldisclosure"
}
],
"descriptions": [
{
"lang": "en",
"value": "0day Rubbish Research Team is publicly disclosing a vulnerability in\nStreamSets Transformer, the Spark-engine data-pipeline platform from\nStreamSets Inc. (subsequently acquired by IBM), verified on version 3.17.0\nanalysed from the official container image.\n\nType: failing-open authentication plus un-sandboxed code injection. On the\nweb tier, CWE-306 and CWE-1188 with CWE-285 on the authorisation side: when\nthe effective http.authentication value resolves to none, the embedded\nservlet container installs no authentication handler at all, and the same\nstate with DPM disabled registers a filter on every path that makes every\nrole check pass and presents a synthesised admin principal. At the sink,\nCWE-94: the REST pipeline API accepts an attacker-chosen pipeline whose\nScalaDTransform code field, an unconstrained text configuration entry, is\ncompiled with the full Scala compiler and executed inside the service JVM,\nwhich runs as uid 0. The research records exactly three absences on that\npath: no SecurityManager, no sandbox and no API allowlist.\n\nScoring. Dual-scored, with the primary reading named first:\n- PRIMARY, as distributed, 8.1 High, vector\n CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Attack complexity\n is high because success depends on a target state the attacker\n does not control: the shipped properties file sets aster, so the\n anonymous state is reached by operator choice or by loss of the property.\n- CONDITIONAL, 9.8 Critical, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H,\n for deployments whose effective mode does resolve to none, including the\n verified instance, where the chain completed deterministically. This is\n the deployment-conditional reading and is not the factory-state rating.\n\nImpact: anonymous code execution as uid 0 inside the container on the first\ncommand, with no escalation step; unrestricted read of every stored pipeline\ndefinition including connection configuration, of the product property\nfiles and of the container filesystem; arbitrary modification of product\nstate; and availability impact on an engine that sits between upstream\nsources and downstream warehouses. No sandbox was bypassed, because none\nexists on the compile-and-run path.\n\nVerification boundary, stated plainly. Verified end to end over plain HTTP\nagainst a live instance of the official container image, three independent\nruns, each leaving a per-run unique root-owned marker file; the identity\ncommand returned uid 0 inside the container and command output was recovered\nout of band from the container filesystem. No instance was exercised at its\nshipped property value, so no bypass of the authenticated configuration is\nclaimed; the property-loss fallback is established from decompiled code\nrather than a live experiment; container root was reached with no escape\nattempted or claimed; only version 3.17.0 was tested. The shipped\nproof-of-concept takes every target detail as a parameter and includes a\nprobe mode that tests the precondition without attacking.\n\nFull technical analysis and a reproducible proof-of-concept:\n https://0day-rubbish.com/blog/streamsets-transformer-auth-none-scaladtransform-code-execution\n\nProject archive (ongoing disclosure series):\n https://github.com/Exploit-Garbage/0day-Rubbish\n\nThe vendor has been notified through the product-security intake the vendor\npublishes for this product line. No vulnerability identifier has been\nassigned to this finding yet.\n\n--\n0day Rubbish Research Team\ndisclosure () 0day-rubbish com\nhttps://0day-rubbish.com\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-1188",
"description": "CWE-1188",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-285",
"description": "CWE-285",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-306",
"description": "CWE-306",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-94",
"description": "CWE-94",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-02T07:30:01Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description",
"exploit"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Oct/8"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Oct/8"
},
{
"url": "https://0day-rubbish.com"
},
{
"url": "https://0day-rubbish.com/blog/streamsets-transformer-auth-none-scaladtransform-code-execution"
},
{
"url": "https://github.com/Exploit-Garbage/0day-Rubbish"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Oct/8"
],
"discovery": "EXTERNAL"
},
"title": "[0day-rubbish] StreamSets Transformer 3.17.0 auth-mode none fallback and un-sandboxed ScalaDTransform execution to container root (8.1 primary)",
"x_gcve": [
{
"recordType": "advisory",
"relationships": [],
"vulnId": "GCVE-1988-2026-0471",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Oct/8",
"automated": true,
"contentSha256": "9deb13716b7abf1a67e3d8976361311f4957d70089ebf8522b2b924ea38b2869",
"evidenceScore": 11,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Oct/8",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-10-05T17:54:04Z"
}
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-11-02T07:30:01Z",
"dateUpdated": "2026-11-02T07:30:01Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0471"
},
"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.