CVE-2023-0835

markdown-pdf 11.0.0 renders user-supplied Markdown without validating it, and that lets an attacker read arbitrary local files off the machine doing the conversion. Because the rendering pulls in whatever the malicious Markdown references, a document crafted by an external user becomes a file-exfiltration primitive, reaching files the rendering process can access. The scope-changed metric reflects that the damage lands outside the component's own boundary.

Anywhere Markdown from one user gets turned into a PDF, comment fields, note-taking features, report generators, this is a live path, and it only needs the attacker to submit content that later gets rendered. It is not a self-propagating exploit, but in a multi-user application it lets an outsider pull secrets and configuration off the server. The value to an attacker is exactly the local files, credentials and keys, that unlock the next stage.

This is a dependency-tracing exercise for us: markdown-pdf is a library embedded in applications, so we need to find which services depend on version 11.0.0 and, of those, which feed it Markdown that any untrusted user can influence. That intersection, vulnerable version plus attacker-reachable input, is the short list that actually matters, and it is far smaller than the raw count of projects that pull the package in.