Changes between Version 3 and Version 4 of SecurityIssues


Ignore:
Timestamp:
Apr 10, 2014, 11:25:25 AM (10 years ago)
Author:
Even Rouault
Comment:

Mention issue with PDF driver

Legend:

Unmodified
Added
Removed
Modified

  • SecurityIssues

    v3 v4  
    5858    * The opening syntax MEM:::DATAPOINTER=some_address can access any valid virtual memory of the process. Feeding it with a random access can cause a crash, or a read of unwanted virtual memory. The MEM driver is used by various algorithms and drivers in creation mode (which is not vulnerable to the DATAPOINTER issue), so completely disabling the driver might be detrimental to other areas of GDAL. It is possible to define the GDAL_NO_OPEN_FOR_MEM_DRIVER *compilation* flag to disable the MEM::::DATAPOINTER= syntax only.
    5959
     60=== [http://gdal.org/frmt_pdf.html GDAL PDF] driver ===
     61    * The OGR_DATASOURCE creation option accepts a file name. So any OGR datasource, and potentially any file (see OGR VRT) could be read through this option, and its content embeded in the generated PDF.
     62
    6063=== [http://www.gdal.org/gdal_vrttut.html GDAL VRT] driver ===
    6164    * Can be used to access any valid GDAL dataset. If a hostile party, with knowledge of the location on the filesystem of a valid GDAL dataset, convinces a victim user to gdal_translate a VRT file and give it back the result, he might be able to steal data.