Mozilla · Firefox
A missing type check when handling fonts in PDF.js, the PDF renderer bundled with Mozilla Firefox, allows arbitrary JavaScript to run in the PDF.js context. An attacker can exploit it over the network with no privileges or user interaction, though the attack is considered high complexity.
Public exploit code (PoC-in-GitHub) appeared 6 days after disclosure. No confirmed exploitation is recorded.
3 related vulnerabilities in the same code over 19 months.
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
This issue is related to CVE-2024-4367, but the root cause of this Nextcloud issue is that the product exposes executable example code on a same-origin basis.
No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
1 package in 1 ecosystem. Main package: pdfjs-dist.
Upgrade to 4.2.67 or later
npm install pdfjs-dist@4.2.67The first fix for CVE-2024-4367. No other CVE tracked by Patchfirst affects this package.
| If you run | Upgrade to |
|---|---|
| All versions before 4.2.67 | 4.2.67 |
“Up to” means the second version is the fix and is not affected.
Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.