GHSA-mq6v-w35g-3c97 json
Local File Inclusion vulnerability in zmarkdown
published 2y ago modified 2y ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Impact
A minor Local File Inclusion vulnerability has been found in `zmarkdown`, which allowed for images with a known path on the host machine to be included inside a LaTeX document.
To prevent it, a new option has been created that allow to replace invalid paths with a default image instead of linking the image on the host directly. `zmarkdown` has been updated to make this setting the default.
Every user of `zmarkdown` is likely impacted, except if disabling LaTeX generation or images download. Here is an example of including an image from an invalid path:
```markdown  ```
Will effectively redownload and include the image found at `/tmp/img.png`.
### Patches
The vulnerability has been patched in version 10.1.3. If impacted, you should update to this version as soon as possible.
### Workarounds
Disable images downloading, or sanitize paths.
### For more information
If you have any questions or comments about this advisory, open an issue in [ZMarkdown](https://github.com/zestedesavoir/zmarkdown/issues).
Patch / fix
- npm zmarkdown 10.1.3
Is GHSA-mq6v-w35g-3c97 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | zmarkdown | <10.1.3 |
10.1.3 |
References
Sources
- GitHub Advisory GHSA-mq6v-w35g-3c97
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.