Live data from Hacker News

50 CVEs in 50 Days: Fuzzing Adobe Reader

research.checkpoint.com

31–40 of 173 posts

Re: 50 CVEs in 50 Days: Fuzzing Adobe Reader

#31
post #15

Earlier quoted context omitted.

Libpoppler has poor support for PDF Forms (especially Unicode[1][2]), embedded animation and 3D extensions. In my opinion these areas are very important in real world document exchange to be ignored (as it is a case for PDF FOSS tools). [1] https://bugs.freedesktop.org/show_bug.cgi?id=17913 [2] https://gitlab.freedesktop.org/poppler/poppler/issues/463

I have never seen anyone use any of these features in the real world. I presume that embedded animation and 3D extensions are used in art-related fields? If so that would explain my ignorance.

PDF forms are used all over the place from what I can tell -- including a bunch of county government stuff I just had to deal with. No JS was involved though.

Re: 50 CVEs in 50 Days: Fuzzing Adobe Reader

#32

Earlier quoted context omitted.

PDFs are supposed to look the same on every computer. Webpages can’t do that yet.

I don't know how accurate that is for PDF's, but webpages are supposed to look the same, and given known compatible styling, it should be on any modern browser. Browsers are extremely consistent in content presentation, that's why webpages from early 2000s still look the same.

[deleted]

Re: 50 CVEs in 50 Days: Fuzzing Adobe Reader

#33

Earlier quoted context omitted.

PDFs are supposed to look the same on every computer. Webpages can’t do that yet.

I don't know how accurate that is for PDF's, but webpages are supposed to look the same, and given known compatible styling, it should be on any modern browser. Browsers are extremely consistent in content presentation, that's why webpages from early 2000s still look the same.

No. Take for example font-family: sans-serif. That can look like anything, can have different widths on different devices, etc. Browser windows can have any size, devices can have various pixel densities, users can work at different zoom levels, etc. The previous big thing was responsive design.

Re: 50 CVEs in 50 Days: Fuzzing Adobe Reader

#34

Earlier quoted context omitted.

PDFs are supposed to look the same on every computer. Webpages can’t do that yet.

I don't know how accurate that is for PDF's, but webpages are supposed to look the same, and given known compatible styling, it should be on any modern browser. Browsers are extremely consistent in content presentation, that's why webpages from early 2000s still look the same.

Web page rendering is far from similar on different browsers. I agreed that an alternative to PDF would be a good thing, but it probably would be more like a lightweight PDF than what HTML is today.

Re: 50 CVEs in 50 Days: Fuzzing Adobe Reader

#35

Do people still use Adobe reader nowadays? Last time that I tried it in my school's library it took half a minute to load and render my document, and after that the whole UI was unresponsive. I had a much better experience with Sumatra on windows and Zathura on Linux where my documents open almost instantly.

.. tried Zathura on LUbuntu just now for the first time ; appears to be a VIM for documents viewing or something.. no interest in Zathura here!

You almost make it sound like a bad thing.

Re: 50 CVEs in 50 Days: Fuzzing Adobe Reader

#37

If you read the PDF spec from the late 90's, it is Stephen King novel-scary... container format, multiple encodings, encryption, embedded binaries, embedded JavaScript and more.

I've done exactly that. Mark my words, a PDF will be the first computer program to gain full sentience.

Re: 50 CVEs in 50 Days: Fuzzing Adobe Reader

#38

If you read the PDF spec from the late 90's, it is Stephen King novel-scary... container format, multiple encodings, encryption, embedded binaries, embedded JavaScript and more.

I was under the impression that PDF was created as a response to postscript being "too programmable" and not "document enough" but then they decided that PDF is too minimal and so they ended up bloating it beyond what PostScript ever was by including JavaScript, Flash, and other trash in it.

It's got a 3d model viewer in it

Re: 50 CVEs in 50 Days: Fuzzing Adobe Reader

#39
post #38

Earlier quoted context omitted.

I was under the impression that PDF was created as a response to postscript being "too programmable" and not "document enough" but then they decided that PDF is too minimal and so they ended up bloating it beyond what PostScript ever was by including JavaScript, Flash, and other trash in it.

It's got a 3d model viewer in it

So does TempleOS.

Re: 50 CVEs in 50 Days: Fuzzing Adobe Reader

#40

If you read the PDF spec from the late 90's, it is Stephen King novel-scary... container format, multiple encodings, encryption, embedded binaries, embedded JavaScript and more.

I've done exactly that. Mark my words, a PDF will be the first computer program to gain full sentience.

Semi-relevant: https://www.xkcd.com/1667/
Post reply on HN