<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 203: fixed-size arrays of size PL_MAXPOLY cause out-of-bound and posible crashes</title><link>https://sourceforge.net/p/plplot/bugs/203/</link><description>Recent changes to 203: fixed-size arrays of size PL_MAXPOLY cause out-of-bound and posible crashes</description><atom:link href="https://sourceforge.net/p/plplot/bugs/203/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 03 Jun 2022 13:32:05 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/plplot/bugs/203/feed.rss" rel="self" type="application/rss+xml"/><item><title>fixed-size arrays of size PL_MAXPOLY cause out-of-bound and posible crashes</title><link>https://sourceforge.net/p/plplot/bugs/203/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;xscl and yscl , used by difilt(), are of size PL_MAXPOLY whereas their contents can be of any size, (see line 534 of plcore) causing invalid memory access and code corruption. &lt;br/&gt;
This is most visible when drawing a filled area of a shape of size &amp;gt; PL_MAXPOLY on the postscript driver, that triggers difilt() due to its (IMHO too complicated) coordinate conversions.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">giloo</dc:creator><pubDate>Fri, 03 Jun 2022 13:32:05 -0000</pubDate><guid>https://sourceforge.net15ea0c287f7cfd76f91573d809c428b3dd84e987</guid></item></channel></rss>