<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 203: fixed-size arrays of size PL_MAXPOLY cause out-of-bound and posible crashes</title><link href="https://sourceforge.net/p/plplot/bugs/203/" rel="alternate"/><link href="https://sourceforge.net/p/plplot/bugs/203/feed.atom" rel="self"/><id>https://sourceforge.net/p/plplot/bugs/203/</id><updated>2022-06-03T13:32:05.861000Z</updated><subtitle>Recent changes to 203: fixed-size arrays of size PL_MAXPOLY cause out-of-bound and posible crashes</subtitle><entry><title>fixed-size arrays of size PL_MAXPOLY cause out-of-bound and posible crashes</title><link href="https://sourceforge.net/p/plplot/bugs/203/" rel="alternate"/><published>2022-06-03T13:32:05.861000Z</published><updated>2022-06-03T13:32:05.861000Z</updated><author><name>giloo</name><uri>https://sourceforge.net/u/gilles-duvert/</uri></author><id>https://sourceforge.net15ea0c287f7cfd76f91573d809c428b3dd84e987</id><summary type="html">&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;</summary></entry></feed>