[postgis-tickets] [PostGIS] #3980: [SFCGAL] Potential access to freed memory

[PostGIS]

#3980: [SFCGAL] Potential access to freed memory
----------------------+---------------------------
  Reporter:  lucasvr  |      Owner:  colivier
      Type:  defect   |     Status:  new
  Priority:  medium   |  Milestone:  PostGIS 2.4.3
 Component:  sfcgal   |    Version:  2.4.x
Resolution:           |   Keywords:
----------------------+---------------------------

Comment (by strk):

 sfcgal_make_solid surely looks unsafe as the PG_FREE_IF_COPY'ed memory is
 accessed by subsequently called serializer, I bet other places are also
 unsafe. It makes sense, IMHO, to simply move the PG_FREE_IF_COPY to after
 the serialization. Up for a patch or git merge request ?

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3980#comment:1>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.