FKIE_CVE-2022-44748
Vulnerability from fkie_nvd - Published: 2022-11-24 07:15 - Updated: 2026-06-17 05:087.5 (High) - CVSS:3.1/
| URL | Tags | ||
|---|---|---|---|
| security@knime.com | https://www.knime.com/security/advisories | Vendor Advisory | |
| af854a3a-2127-422b-91ae-364da2661108 | https://www.knime.com/security/advisories | Vendor Advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| knime | knime_server | * | |
| knime | knime_server | * | |
| knime | knime_server | * |
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "KNIME Server",
"vendor": "KNIME",
"versions": [
{
"lessThan": "4.15.3",
"status": "affected",
"version": "4.15.0",
"versionType": "semver"
},
{
"lessThan": "4.14.3",
"status": "affected",
"version": "4.14.0",
"versionType": "semver"
},
{
"lessThan": "4.13.6",
"status": "affected",
"version": "4.3.0",
"versionType": "semver"
}
]
}
],
"source": "security@knime.com"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:knime:knime_server:*:*:*:*:*:*:*:*",
"matchCriteriaId": "494D779C-C6DB-46F9-9A52-932BD303F938",
"versionEndExcluding": "4.13.6",
"versionStartIncluding": "4.3.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:knime:knime_server:*:*:*:*:*:*:*:*",
"matchCriteriaId": "0CD9DC54-5478-4D9C-987F-62BCD2E9D6B8",
"versionEndExcluding": "4.14.3",
"versionStartIncluding": "4.14.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:knime:knime_server:*:*:*:*:*:*:*:*",
"matchCriteriaId": "A57784CC-3757-4509-9491-037B3947784D",
"versionEndExcluding": "4.15.3",
"versionStartIncluding": "4.15.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "A directory traversal vulnerability in the ZIP archive extraction routines of KNIME Server since 4.3.0 can result in arbitrary files being overwritten on the server\u0027s file system. This vulnerability is also known as \u0027Zip-Slip\u0027.\n\n\n\n\n\nAn attacker can create a KNIME workflow that, when being uploaded, can overwrite arbitrary files that the operating system user running the KNIME Server process has write access to. The user must be authenticated and have permissions to upload files to KNIME Server.\n\n\nThis can impact data integrity (file contents are changed) or cause errors in other software (vital files being corrupted). It can even lead to remote code execution if executable files are being replaced and subsequently executed by the KNIME Server process user. In all cases the attacker has to know the location of files on the server\u0027s file system, though.\n\nNote that users that have permissions to upload workflows usually also have permissions to run them on the KNIME Server and can therefore already execute arbitrary code in the context of the KNIME Executor\u0027s operating system user.\n\nThere is no workaround to prevent this vulnerability from being exploited. Updates to fixed versions 4.13.6, 4.14.3, or 4.15.3 are advised.\n\n\n"
},
{
"lang": "es",
"value": "Una vulnerabilidad de directory traversal en las rutinas de extracci\u00f3n de archivos ZIP de KNIME Server desde 4.3.0 puede provocar la sobrescritura de archivos arbitrarios en el sistema de archivos del servidor. Esta vulnerabilidad tambi\u00e9n se conoce como \u0027Zip-slip\u0027. Un atacante puede crear un flujo de trabajo KNIME que, cuando se carga, puede sobrescribir archivos arbitrarios a los que el usuario del sistema operativo que ejecuta el proceso del servidor KNIME tiene acceso de escritura. El usuario debe estar autenticado y tener permisos para cargar archivos al servidor KNIME. Esto puede afectar la integridad de los datos (se modifica el contenido de los archivos) o provocar errores en otro software (se da\u00f1an archivos vitales). Incluso puede conducir a la ejecuci\u00f3n remota de c\u00f3digo si el usuario del proceso del servidor KNIME reemplaza los archivos ejecutables y posteriormente los ejecuta. Sin embargo, en todos los casos el atacante debe conocer la ubicaci\u00f3n de los archivos en el sistema de archivos del servidor. Tenga en cuenta que los usuarios que tienen permisos para cargar flujos de trabajo generalmente tambi\u00e9n tienen permisos para ejecutarlos en el servidor KNIME y, por lo tanto, ya pueden ejecutar c\u00f3digo arbitrario en el contexto del usuario del sistema operativo del ejecutor KNIME. No existe ninguna soluci\u00f3n alternativa para evitar que se aproveche esta vulnerabilidad. Se recomiendan actualizaciones a las versiones fijas 4.13.6, 4.14.3 o 4.15.3."
}
],
"id": "CVE-2022-44748",
"lastModified": "2026-06-17T05:08:52.923",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 4.2,
"source": "security@knime.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.6,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2022-44748",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-04-25T18:00:15.646079Z",
"version": "2.0.3"
}
}
]
},
"published": "2022-11-24T07:15:09.973",
"references": [
{
"source": "security@knime.com",
"tags": [
"Vendor Advisory"
],
"url": "https://www.knime.com/security/advisories"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Vendor Advisory"
],
"url": "https://www.knime.com/security/advisories"
}
],
"sourceIdentifier": "security@knime.com",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-22"
}
],
"source": "security@knime.com",
"type": "Secondary"
},
{
"description": [
{
"lang": "en",
"value": "CWE-22"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
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.