The pdf_to_num function in pdf-object.c in MuPDF before 1.10 allows remote attackers to cause a denial of service (use-after-free and application crash) via a crafted file.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
| Link | Tags |
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=1385685 | issue tracking patch |
| https://bugs.ghostscript.com/show_bug.cgi?id=697019 | issue tracking patch |
| http://www.securityfocus.com/bid/93127 | vdb entry third party advisory |
| http://www.debian.org/security/2017/dsa-3797 | vendor advisory |
| http://www.openwall.com/lists/oss-security/2016/10/16/8 | mailing list third party advisory patch |
| https://bugs.ghostscript.com/show_bug.cgi?id=697015 | issue tracking patch |
| http://git.ghostscript.com/?p=mupdf.git%3Ba=commitdiff%3Bh=1e03c06456d997435019fb3526fa2d4be7dbc6ec | |
| https://blogs.gentoo.org/ago/2016/09/22/mupdf-use-after-free-in-pdf_to_num-pdf-object-c/ | vdb entry third party advisory patch |