CVE-2026-59941— dompdf 资源管理错误漏洞

Dompdf: Uncontrolled resource consumption based on declared BMP dimensions

Dompdf is an HTML to PDF converter for PHP. Versions 3.15 and prior accept a BMP image and generates a PDF-compatible PNG based only on its declared header dimensions and never bounds width × height before the image is converted through GD. A 58-byte BMP whose header declares e.g. 6000×6000 is accepted and later drives imagecreatetruecolor($width, $height) (and PHP's native BMP decoder) to allocate the full pixel canvas. A payload can fit in a single HTTP request: the BMP can be inlined as a data:image/bmp;base64,… URI inside attacker-controlled HTML, so no upload, no remote fetch, and no chroot-reachable file is required. I measured a 169-byte request driving a dompdf render to ~412 MB peak RSS and ~4.8 s of CPU/wall time, versus ~34 MB for an identically-sized benign request — roughly a 12× memory amplification per request, repeatable and unauthenticated. This issue has been fixed in version 3.16.

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

未加控制的资源消耗(资源穷尽)

dompdf 资源管理错误漏洞

dompdf是dompdf团队开源的一个 HTML 到 PDF 的转换器。 dompdf 3.16之前版本存在资源管理错误漏洞，该漏洞源于接受BMP图像时仅依据声明的头部尺寸生成PNG，未限制宽高，导致通过GD分配完整像素画布，造成内存放大，可能导致拒绝服务。

N/A

N/A