GCVE-1988-2026-0497
Vulnerability from gna-1988 – Published: 2026-11-02 07:30 – Updated: 2026-11-02 07:30| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| unknown | Parasoft Continuous Testing |
Affected:
unknown
|
guessed |
{
"containers": {
"cna": {
"affected": [
{
"product": "Parasoft Continuous Testing",
"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 Parasoft\nContinuous Testing Platform 10.7.5-SNAPSHOT, the closed-source commercial\ncontinuous-testing, service-virtualisation and environment-management product\nfrom Parasoft, a United States software-testing vendor headquartered in\nMonrovia, California. The affected component is the em web application inside\nthe vendor\u0027s own container image, running on Tomcat 10.1.57 with Jasper and\nJava 17. Three first-party defects compose into an unauthenticated\ncommand-execution chain that needs two HTTP requests and nothing else: an\nunfiltered ObjectInputStream over an uploaded backup archive, a licensing\nfilter that decides whether to run at all by testing the raw un-normalised\nrequest URI, and a remember-me authentication service that hands an anonymous\nrequest an authenticated administrator principal when no external security\nprovider has been configured.\n\nType and root cause. Unfiltered deserialization of attacker-controlled data,\nCWE-502 primary, composed with an interpretation conflict in the licensing\nfilter, CWE-436 primary and co-equal with CWE-863 as its authorisation\nconsequence, and enabled by a fail-open authentication branch, CWE-287. The\nhonest count is three first-party defects rather than one, and that matters to\nwhoever fixes it, because the defect owners, the fixes and the independent\nvalue to an attacker all differ.\n\nThe licensing defect. EMLicenseFilter is 175 lines and behaves as an\nauthorisation boundary, being what stops an unlicensed instance from serving\nits administrative API. Its decision procedure reads the request URI raw at\nline 165 and tests it at line 166 against a chain of exemption clauses\nincluding endsWith(\"about\"), endsWith(\"welcome\"), endsWith(\"forgot\"),\nendsWith(\"notlicensed\"), contains(\"/resources/\") and contains(\"/images/\"),\nnone of which is anchored by a separator or a segment boundary. A branch at\nlines 167 to 171 additionally reassigns the whole exemption set rather than\naccumulating into it when the request accepts JSON. The test has exactly one\nconsumer in the class: shouldNotFilter() at line 47 calling isLicenseRequired()\nat line 48. So a matching URI does not weaken one decision, it suppresses the\nentire doFilterInternal() body, including the /tdm/api/v guard at line 99 and\nthe unlicensed-instance redirect to /em/license at line 118. Because a servlet\ncontainer strips semicolon-delimited path parameters from each segment before\nit performs servlet mapping, the filter and the router disagree about the\nidentity of one request: a target of /em/database/restore;welcome is exempted\nby the filter and still routed to the restore handler by the container. That\ndisagreement is the textbook shape of CWE-436. Measured read-only on a live\ninstance, with the control that carries the argument:\n\n GET /em/database/currentConfig\n -\u003e 302, Location: /em/license, zero-length body\n GET /em/database/currentConfig;welcome\n -\u003e 200, 204 bytes, application/json;charset=utf-8, disclosing the\n schema version, the HyperSQL type, the database user and the\n jdbc:hsqldb:file URL of the platform\u0027s own database files\n GET /em/database/currentConfig;about\n -\u003e the same 200/204, so this is the clause list and not one word\n GET /em/database/currentConfigwelcome (no semicolon)\n -\u003e 404, 792 bytes\n GET /em/tdm/api/v2/servers;welcome\n -\u003e 200, 160 bytes, a well-formed serversResponse XML document with an\n empty servers element, so Jersey routed and ran the resource method\n the same pair over TLS\n -\u003e 200/204 with the bypass and 302/0 without it, so the HTTPS\n listener is an equivalent surface and not a redirect shell\n\nThe no-semicolon control is the load-bearing row: the only variable that\nchanged is the presence of a semicolon path parameter, and the outcome flipped\nfrom a licensing redirect to a 200 carrying live database configuration to a\ncaller who had never authenticated. The bypass is not a skeleton key, and that\nwas measured rather than assumed: handlers performing their own licensing\ncheck are unaffected, the coverage-agent endpoints reading the license manager\ndirectly and continuing to return 403 with a 90-byte unlicensed body across all\nseventeen of their mappings even with the bypass applied, while a server-resource\nfeature gate kept returning 403 with a 94-byte body. What the bypass unlocks is\neverything whose enforcement lives only in the filter, which includes the whole\n/em/database subtree and the entire /em/tdm/api/v version tree. One related\nfirst-party defect sits in the same filter and matters for detection: line 113\nflushes the response output stream and line 115 then calls setStatus(403), so\nlicence refusals surface as HTTP 200 with a JSON body carrying status 403,\nwhich makes them invisible to any status-based monitoring.\n\nThe deserialization defect. The restore path lands in\ncom.parasoft.ctp.core.database.backup.AbstractDatabaseBackup, a class of 518\nlines and 19,851 bytes:\n\n :14 import java.io.ObjectInputStream;\n :111 ObjectInputStream ois = new ObjectInputStream(in);\n :112 int numTables = ois.readInt();\n :117 TableMetadata tableMetadata = (TableMetadata) ois.readObject();\n :126 Connection connection = this.provider.getConnection();\n\nwhere in is the database.ser member of an uploaded zip. Three properties are\ndecisive. The cast is applied to whatever readObject() returned, so it\nconstrains nothing: the gadget executes during the call and the\nClassCastException is thrown afterwards. getConnection() sits nine lines\nlower, so no database needs to exist, to be reachable or to accept the supplied\nparameters for the payload to have already run, which makes that ordering the\ncheapest structural fix available and one needing no understanding of gadget\nchains. And the int read at line 112 is consumed before the object read. The\ncaller is the web-layer controller EMDatabaseController, 1359 lines, whose\nrestore handler at line 707 or 708 takes a StandardMultipartHttpServletRequest\nand hard-compares zip member names against the literals \"version.txt\" at line\n725 and \"database.ser\" at line 733, a shape check that says nothing about\ncontent. The absence of any filter is not an inference from one search: in the\nwhole shipped product ObjectInputStream appears in 68 files with 149 occurrences\nin the core tree and in 3 files in the web layer, readObject appears in 81\nfiles, and ObjectInputFilter appears in 0 files, jdk.serialFilter in 0 files and\nserialFilter in 0 files. Three zeros, across a class name, a system property and\nits short alias, in an image unpacked and searched as artefacts against a\npositive control of 81 files containing readObject, is a strong result: the\nproduct has no deserialization filtering anywhere in its construction. Two\nsibling readObject() calls on the same class of untrusted stream sit in the same\nfile at lines 323 and 435, in a row-draining routine and a row-binding routine;\nthey were read from source and not detonated, and they are named so a fix covers\nthe class rather than the call site.\n\nThe fail-open authentication gate. The application has three Spring Security\nfilter chains and all three register the same remember-me service,\nEMRememberMeServices, 483 lines, with the security configuration in\nCTPSecurityWebConfig, 318 lines. Neither hop of the chain is an unprotected\nroute: /database is explicitly matched to authenticated(), and the images\nallow-list is /images/welcome/star rather than a doubled-asterisk glob over\n/images, so a page written to images/\u003cleaf\u003e.jsp also needs an authenticated\nsubject at the security layer. Both hops sit behind the authentication\nboundary. The finding is therefore described accurately as the product handing\nan anonymous request an authenticated administrative principal:\n\n // EMRememberMeServices.java:140-148, abridged\n if (request.getHeader(\"Authorization\") != null) {\n return null; // :140-142 defer to credentials\n }\n pstsecClient = PSTSecServiceClient.getInstance(); // :146\n if (pstsecClient == null) { // :148 the fail-open branch\n return this.createAuthenticationToken(\"admin\", \"admin\",\n EmUserInfo.Role.ADMIN, request);\n }\n\nThe token registers new SimpleGrantedAuthority(\"ROLE_ADMIN\") and wraps it in a\nSpring Security User whose authenticated flag is true, so the resulting\nprincipal is a genuinely authenticated administrator rather than the container\u0027s\nanonymous principal, and the authenticated() matcher that CTPSecurityWebConfig\nline 283 demands for /database is satisfied by it. The condition guarding all of\nthis is the absence of the external security-provider client, which in the\nuntouched vendor image, with no setup step performed, does not exist. Measured\nwith its control in the same run: an anonymous GET of the users/current resource\nunder the /em/api/v3 context returned 200 with the 39-byte body\n{\"id\":1,\"login\":\"admin\",\"role\":\"ADMIN\"}, and the identical request carrying\nAuthorization: Bearer garbage returned 401 with an empty body. The control shows\nthe fail-open branch is specific to requests presenting no credential at all, so\nthe behaviour is not \"authentication is off\" but \"an absent credential is more\ntrusted than a wrong one\". CSRF is separately not an obstacle, because\nCsrfSecurityRequestMatcher is a 28-line class whose anchored exemption alternation\nat line 19 includes /database, with GET, HEAD, TRACE and OPTIONS exempt by method\nat line 22.\n\nThe write primitive and the execution sink. Reconstituting the stream\u0027s first\nobject, a java.util.HashSet, forces a hashCode() on its single element, a\nTiedMapEntry wrapping a LazyMap whose transformer factory is a\nConstantTransformer holding attacker bytes and whose decorated map is an\naspectjweaver SimpleCache$StoreableCachingMap whose folder field is an absolute\npath:\n\n readObject() -\u003e HashSet.readObject -\u003e HashMap.putVal -\u003e key.hashCode()\n -\u003e commons-collections4 TiedMapEntry.hashCode() -\u003e getValue()\n -\u003e commons-collections4 LazyMap.get(key) // transform the key\n -\u003e map.put(key, value) // invokeinterface, virtual dispatch\n -\u003e aspectjweaver SimpleCache$StoreableCachingMap.put(key, byte[])\n -\u003e writeToPath(folder + File.separator + key, bytes)\n\nThat class was read at the bytecode level to establish four facts, all of which\nare what make the write arbitrary. The folder field is declared private final\nString, is not transient, and the class declares no readObject of its own, so it\nis populated by the inherited HashMap.readObject path through defaultReadObject,\nwhich assigns whatever the stream carries, and both writeToPath and the store\nroutine read it with an explicit getfield so the compiler has not inlined it.\nwriteToPath performs getfield folder, builds a StringBuilder, concatenates a\nseparator and the key, and stores the result, which is the entire function: there\nis no forced extension appended to the key, and the value passes a checkcast to a\nbyte array, so the content is any bytes at all. Validation is absent in every\nform, with zero occurrences of File.getName(), Path.normalize(),\ngetCanonicalPath(), startsWith(), a regular expression or a length truncation in\nthat write path; keys carrying slashes or relative traversals both work, and\nbecause concatenation with an empty folder yields a leading double separator,\nwhich POSIX treats as a valid absolute path, an absolute destination is reachable\ntoo. And it does not fire on deserialization alone, which is the subtle part:\nHashMap.readObject reconstitutes entries through putVal, package-private, final\nand not overridden, so it bypasses the overridden put that contains the write,\nwhich is why the TiedMapEntry to LazyMap to Map.put prefix is needed to force a\nvirtual dispatch. The only content constraint found anywhere is that the bytes\nmust not be exactly the four-byte sentinel IDEM. In the publish"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-22",
"description": "CWE-22",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-287",
"description": "CWE-287",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-321",
"description": "CWE-321",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-347",
"description": "CWE-347",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-436",
"description": "CWE-436",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-502",
"description": "CWE-502",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-863",
"description": "CWE-863",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-02T07:30:03Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description",
"exploit"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Oct/31"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Oct/31"
},
{
"url": "https://0day-rubbish.com"
},
{
"url": "https://0day-rubbish.com/blog/parasoft-ctp-unfiltered-deserialization-license-gate-fail-open-jsp-rce"
},
{
"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/31"
],
"discovery": "EXTERNAL"
},
"title": "[0day-rubbish] Parasoft Continuous Testing Platform 10.7.5-SNAPSHOT anonymous deserialization in the database restore path to JSP command execution as uid=1000 (9.8)",
"x_gcve": [
{
"recordType": "advisory",
"relationships": [],
"vulnId": "GCVE-1988-2026-0497",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Oct/31",
"automated": true,
"contentSha256": "1ae367abb7434ab326ae800e7fd8fba011e44b76212130d268d07a97c6132955",
"evidenceScore": 11,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Oct/31",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-10-20T02:31:02Z"
}
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-11-02T07:30:03Z",
"dateUpdated": "2026-11-02T07:30:03Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0497"
},
"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.