Mammoth is vulnerable to Directory Traversal
mammoth · Mammoth · org.zwobble.mammoth:mammoth
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| mammoth npm |
|
|
| org.zwobble.mammoth:mammoth Maven |
|
|
| mammoth PyPI |
mammoth · Mammoth · org.zwobble.mammoth:mammoth
| Product | Affected | Fixed in |
|---|---|---|
| mammoth npm |
|
|
| org.zwobble.mammoth:mammoth Maven |
|
|
| mammoth PyPI |
≥ 0.3.25 · < 1.11.0
|
| Mammoth NuGet |
|
|
Versions of the package mammoth from 0.3.25 and before 1.11.0; versions of the package mammoth from 0.3.25 and before 1.11.0; versions of the package mammoth before 1.11.0; versions of the package org.zwobble.mammoth:mammoth before 1.11.0 are vulnerable to Directory Traversal due to the lack of path or file type validation when processing a docx file containing an image with an external link (r:link attribute instead of embedded r:embed). The library resolves the URI to a file path and after reading, the content is encoded as base64 and included in the HTML output as a data URI. An attacker can read arbitrary files on the system where the conversion is performed or cause an excessive resources consumption by crafting a docx file that links to special device files such as /dev/random or /dev/zero.
From the CVE record · snyk
Mammoth does not validate paths or file types when processing a DOCX image with an external link. If an application converts an attacker-crafted DOCX file, the attacker can cause it to read arbitrary files on the conversion system and include their contents in the HTML output, or consume excessive resources by linking to special device files.
Check applications using npm or PyPI mammoth versions 0.3.25 to before 1.11.0, or NuGet Mammoth or Maven org.zwobble.mammoth:mammoth versions before 1.11.0.