How does Adobe allow this to happen? After enough of these over time, you'd think they'd fine some way to invest majorly in securing their runtimes.... either via another language like Mozilla is doing with Rust, some provably secure math-vm-thingie like Microsoft Research, massive security reviews & reduction of attack surfaces like OpenBSD, or another CS-driven solution.
Adobe CVEs
11–20 of 23 posts
Re: Adobe CVEs
#12Looking at crazy stuff like this, I'm so glad most browsers can render PDFs natively and I don't have to rely on any Adobe software anymore.
OK, but then again: https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=chrome+pdf
If you look closer at the pdfium vulns (I reported some of those) they include all kinds of "safety violations" with unclear impact. E.g. integer overflows, invalid memory reads etc. Many of those are simply undetectable without source-level check tools (mostly the C sanitizers).
The Chrome team has a policy of counting a lot of stuff as vulns if it "could" cause a security issue. This is good - better safe than sorry. But it blows up their CVE count and makes them look bad for people doing bad statistics.
Re: Adobe CVEs
#13Earlier quoted context omitted.
OK, but then again: https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=chrome+pdf
Versus Firefox': https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=pdf.js
Re: Adobe CVEs
#14Looking at crazy stuff like this, I'm so glad most browsers can render PDFs natively and I don't have to rely on any Adobe software anymore.
The vastly lower attack surface in PDF viewers built into browsers has been quite frustrating for me. I've seen Adobe vulnerabilities in the wild, and I've seen the improvements to an organisations security by removing Adobe Reader. Not to mention, the immediate reduction in labour of managing its colossal updates regularly. However, try to remove Adobe PDF in a business with more than a few people, and ime, it's onl…
Re: Adobe CVEs
#15How does Adobe allow this to happen? After enough of these over time, you'd think they'd fine some way to invest majorly in securing their runtimes.... either via another language like Mozilla is doing with Rust, some provably secure math-vm-thingie like Microsoft Research, massive security reviews & reduction of attack surfaces like OpenBSD, or another CS-driven solution.
Adobe would definitely profit from languages such as Rust. But they are not a "tech" company in the traditional sense anymore, I don't see them investing in anything that doesn't yield high short term returns. It's a big company that dominates the "creative" market, because it can impose its formats on an industry that does not care about open technologies.
Re: Adobe CVEs
#16Looking at crazy stuff like this, I'm so glad most browsers can render PDFs natively and I don't have to rely on any Adobe software anymore.
Obviously there are legitimate concerns about security with browser plugins, but replacing them with half-baked built-in alternatives isn't going well so far.
Re: Adobe CVEs
#17Earlier quoted context omitted.
Versus Firefox': https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=pdf.js
Firefox is so utterly underrated these days. Such a shame. It's a good browser which puts the user in control and just gets the job done.
Re: Adobe CVEs
#18Earlier quoted context omitted.
Firefox is so utterly underrated these days. Such a shame. It's a good browser which puts the user in control and just gets the job done.
They've been moving away from that though, try changing your user agent or disabling JavaScript.
Re: Adobe CVEs
#19How does Adobe allow this to happen? After enough of these over time, you'd think they'd fine some way to invest majorly in securing their runtimes.... either via another language like Mozilla is doing with Rust, some provably secure math-vm-thingie like Microsoft Research, massive security reviews & reduction of attack surfaces like OpenBSD, or another CS-driven solution.
Their customers don't care and they are not altruistic like Mozilla or OpenBSD.
Re: Adobe CVEs
#20Earlier quoted context omitted.
Adobe would definitely profit from languages such as Rust. But they are not a "tech" company in the traditional sense anymore, I don't see them investing in anything that doesn't yield high short term returns. It's a big company that dominates the "creative" market, because it can impose its formats on an industry that does not care about open technologies.
Rust isn't a cure-all for every security issue.