Open GoogleCodeExporter opened 9 years ago
Is this the same vulnerability identified in issue 177?
Original comment by eclecticgeek
on 24 Jul 2012 at 6:09
No this is a separate issue. I have responded via email with more details about
the potential hack
Original comment by chris.ha...@sa.gov.au
on 26 Jul 2012 at 12:16
Original comment by eclecticgeek
on 27 Jul 2012 at 1:19
Can anyone provide details for this exploit? The benefits of open source
include finding all the holes so they may be patched...
Original comment by msenatea...@gmail.com
on 19 Nov 2012 at 9:16
We will update this issue with details on the exploit once we correct the
problem. The issue lies in the support scripts (namely the included web
content). You can avoid the problem by placing dompdf in a directory not
accessible via the web.
Please note that the issue is not as serious as the previously-disclosed remote
file inclusion exploit.
Original comment by eclecticgeek
on 20 Nov 2012 at 2:39
Original comment by eclecticgeek
on 24 May 2013 at 3:00
Original issue reported on code.google.com by
chris.ha...@sa.gov.au
on 24 Jul 2012 at 2:58