1 2 3 4 5<!DOCTYPE html> 6<html lang="en"> 7<head> 8 <meta charset="utf-8" /> 9 <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1,shrink-to-fit=no" /> 10 <title>Security Policy @ ImageMagick</title> 11 <meta name="application-name" content="ImageMagick" /> 12 <meta name="description" content="Use ImageMagick® to create, edit, compose, or convert bitmap images. You can resize your image, crop it, change its shades and colors, add captions, among other operations." /> 13 <meta name="application-url" content="https://imagemagick.org" /> 14 <meta name="generator" content="PHP" /> 15 <meta name="keywords" content="security, policy, ImageMagick, PerlMagick, image processing, image, photo, software, Magick++, OpenMP, convert" /> 16 <meta name="rating" content="GENERAL" /> 17 <meta name="robots" content="INDEX, FOLLOW" /> 18 <meta name="generator" content="ImageMagick Studio LLC" /> 19 <meta name="author" content="ImageMagick Studio LLC" /> 20 <meta name="revisit-after" content="2 DAYS" /> 21 <meta name="resource-type" content="document" /> 22 <meta name="copyright" content="Copyright (c) 1999-2019 ImageMagick Studio LLC" /> 23 <meta name="distribution" content="Global" /> 24 <meta name="magick-serial" content="P131-S030410-R485315270133-P82224-A6668-G1245-1" /> 25 <meta name="google-site-verification" content="_bMOCDpkx9ZAzBwb2kF3PRHbfUUdFj2uO8Jd1AXArz4" /> 26 <link href="../www/security-policy.html" rel="canonical" /> 27 <link href="../images/wand.png" rel="icon" /> 28 <link href="../images/wand.ico" rel="shortcut icon" /> 29 <link href="assets/magick.css" rel="stylesheet" /> 30</head> 31<body> 32 <header> 33 <nav class="navbar navbar-expand-md navbar-dark fixed-top bg-dark"> 34 <a class="navbar-brand" href="../index.html"><img class="d-block" id="icon" alt="ImageMagick" width="32" height="32" src="../images/wand.ico"/></a> 35 <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarsMagick" aria-controls="navbarsMagick" aria-expanded="false" aria-label="Toggle navigation"> 36 <span class="navbar-toggler-icon"></span> 37 </button> 38 39 <div class="navbar-collapse collapse" id="navbarsMagick" style=""> 40 <ul class="navbar-nav mr-auto"> 41 <li class="nav-item "> 42 <a class="nav-link" href="../index.html">Home <span class="sr-only">(current)</span></a> 43 </li> 44 <li class="nav-item "> 45 <a class="nav-link" href="download.html">Download</a> 46 </li> 47 <li class="nav-item "> 48 <a class="nav-link" href="command-line-tools.html">Tools</a> 49 </li> 50 <li class="nav-item "> 51 <a class="nav-link" href="command-line-processing.html">Command-line</a> 52 </li> 53 <li class="nav-item "> 54 <a class="nav-link" href="resources.html">Resources</a> 55 </li> 56 <li class="nav-item "> 57 <a class="nav-link" href="develop.html">Develop</a> 58 </li> 59 <li class="nav-item"> 60 <a class="nav-link" target="_blank" href="https://imagemagick.org/discourse-server/">Community</a> 61 </li> 62 </ul> 63 <form class="form-inline my-2 my-lg-0" action="https://imagemagick.org/script/search.php"> 64 <input class="form-control mr-sm-2" type="text" name="q" placeholder="Search" aria-label="Search"> 65 <button class="btn btn-outline-success my-2 my-sm-0" type="submit" name="sa">Search</button> 66 </form> 67 </div> 68 </nav> 69 <div class="container"> 70 <script async="async" src="http://localhost/pagead/js/adsbygoogle.js"></script> <ins class="adsbygoogle" 71 style="display:block" 72 data-ad-client="ca-pub-3129977114552745" 73 data-ad-slot="6345125851" 74 data-ad-format="auto"></ins> 75 <script> 76 (adsbygoogle = window.adsbygoogle || []).push({}); 77 </script> 78 79 </div> 80 </header> 81 <main class="container"> 82 <div class="magick-template"> 83<div class="magick-header"> 84<p class="text-center"><a href="security-policy.html#policy">Security Policy </a> • <a href="security-policy.html#synchronize">Pixel Cache Synchronize Policy</a> • <a href="security-policy.html#zero-configuration">Zero Configuration Security Policy</a> • <a href="security-policy.html#other">Other Security Considerations</a></p> 85 86 87<p class="lead magick-description">ImageMagick best practices strongly encourages you to configure a security <a href="https://imagemagick.org/source/policy.xml">policy.xml</a> that suits your local environment. The policy is open by default. This affords maximum utility for ImageMagick installations that run in a sandboxed environment, perhaps in a Docker instance, or behind a firewall where security risks are greatly diminished as opposed to a public website.</p> 88 89<p>Security is a trade-off between a secure environment and convenience. If you want ImageMagick to be optimally secure, you could, for example, limit ImageMagick to only read or write web safe images (e.g. GIF, JPEG, PNG). However, ImageMagick provides for a more secure option by adjusting the security policy per the requirements of your local environment or organizational policies. The security policy covers areas such as memory, which paths to read or write, how many images are permitted in an image sequence, how long a workflow can run, how much disk the image pixels can consume, a secret passphrase for remote connections, which coders are permitted or denied, and others. These policies should provide robust coverage to not only secure your environment per your requirements but also ensure ImageMagick remains a good citizen (e.g. prevent thrashing with large images) in your local environment.</p> 90 91<p>As an example, suppose you download an image from the internet and unbeknownst to you its been crafted to generate a 20000 by 20000 pixel image. ImageMagick attempts to allocate enough resources (memory, disk) and your system will likely deny the resource request and exit. However, its also possible that your computer might be temporarily sluggish or unavailable or ImageMagick may abort. To prevent such a scenario, you can set limits in the <code>policy.xml</code> configuration file. You might wonder why ImageMagick does not already include reasonable limits? Simply because what is reasonable in your environment, might not be reasonable to someone else. For example, you may have ImageMagick sandboxed where security is not a concern, whereas another user may use ImageMagick to process images on their publically accessible website. Or ImageMagick runs on a host with 1TB of memory whereas another ImageMagick instance runs on an iPhone. By policy, permitting giga-pixel image processing on the large memory host makes sense, not so much for the resource constrained iPhone. If you utilize ImageMagick from a public website, you may want to increase security by preventing usage of the MVG or HTTPS coders. Only you can decide what are reasonable limits taking in consideration your environment. We provide this policy with reasonable limits and encourage you to modify it to suit your local environment:</p> 92 93<pre class="pre-scrollable"><code><policymap> 94 <policy domain="resource" name="temporary-path" value="/tmp"/> 95 <policy domain="resource" name="memory" value="256MiB"/> 96 <policy domain="resource" name="map" value="512MiB"/> 97 <policy domain="resource" name="width" value="8KP"/> 98 <policy domain="resource" name="height" value="8KP"/> 99 <policy domain="resource" name="area" value="16KP"/> 100 <policy domain="resource" name="disk" value="1GiB"/> 101 <policy domain="resource" name="file" value="768"/> 102 <policy domain="resource" name="thread" value="2"/> 103 <policy domain="resource" name="throttle" value="0"/> 104 <policy domain="resource" name="time" value="120"/> 105 <policy domain="resource" name="list-length" value="128"/> 106 <policy domain="system" name="precision" value="6"/> 107 <policy domain="cache" name="shared-secret" stealth="true" value="replace with your secret phrase"/> 108 <policy domain="coder" rights="none" pattern="MVG" /> 109 <policy domain="coder" rights="none" pattern="EPS" /> 110 <policy domain="coder" rights="none" pattern="PS" /> 111 <policy domain="coder" rights="none" pattern="PS2" /> 112 <policy domain="coder" rights="none" pattern="PS3" /> 113 <policy domain="coder" rights="none" pattern="PDF" /> 114 <policy domain="coder" rights="none" pattern="XPS" /> 115 <policy domain="filter" rights="none" pattern="*" /> 116 <policy domain="delegate" rights="none" pattern="HTTPS" /> <!-- prevent 'curl' program from reading HTTPS URL's --> 117 <policy domain="path" rights="none" pattern="@*"/> <!-- indirect reads not permitted --> 118</policymap></code></pre> 119 120<p>Since we process multiple simultaneous sessions, we do not want any one session consuming all the available memory. With this policy, large images are cached to disk. If the image is too large and exceeds the pixel cache disk limit, the program exits. In addition, we place a time limit to prevent any run-away processing tasks. If any one image has a width or height that exceeds 8192 pixels or if an image sequence exceeds 128 frames, an exception is thrown and processing stops. As of ImageMagick 7.0.1-8 and 6.9.4-6, you can prevent the use of any delegate or all delegates (set the pattern to "*"). Note, prior to these releases, use a domain of <code>coder</code> to prevent delegate usage (e.g. <code>domain="coder" rights="none" pattern="HTTPS"</code>). We prevent users from executing any image filters. The policy also prevents indirect reads. If you want to, for example, read text from a file (e.g. <code>caption:@myCaption.txt</code>), you'll need to disable the <code>path</code> policy.</p> 121 122<p>Policy patterns are <em>case sensitive</em>. To get expected behavior, coders and modules must be upper-case (e.g. "EPS" not "eps").</p> 123 124<p>Here is what you can expect when you restrict the HTTPS coder, for example:</p> 125 126<pre class="highlight">-> convert ../images/wizard.png wizard.jpg 127convert: attempt to perform an operation not allowed by the security policy `HTTPS' 128convert: unable to open file: No such file or directory 129convert: no images defined `wizard.jpg'</pre> 130 131<p>As of ImageMagick version 7.0.4-7, you can conveniently deny access to all delegates and coders except for a small subset of proven web-safe image types. For example,</p> 132 133<pre class="highlight"><code><policy domain="delegate" rights="none" pattern="*" /> 134<policy domain="coder" rights="none" pattern="*" /> 135<policy domain="coder" rights="read | write" pattern="{GIF,JPEG,PNG,WEBP}" /></code></pre> 136 137<p>Here we disable just a few Postscript related formats:</p> 138<pre class="highlight"><code><policy domain="coder" rights="none" pattern="{EPS,PS2,PS3,PS,PDF,XPS}" /></code></pre> 139 140<p>As of ImageMagick 7.0.7-0, you can allocate the pixel cache and some internal buffers with anonymous memory mapping rather than from heap. As a consequence, the pixels are initialized to zero. You can also securely delete any temporary files for increased security. The value is the number of times to shred (replace its content with random data) before deleting a temporary file. For example,</p> 141<pre class="highlight"><code><policy domain="system" name="memory-map" value="anonymous"/> 142<policy domain="cache" name="memory-map" value="anonymous"/> 143<policy domain="system" name="shred" value="1"/></code></pre> 144 145<p>Some image processing algorithms (e.g. wavelet transform) might consume a substantial amount of memory to complete. ImageMagick maintains a separate memory pool for these large resource requests and as of 7.0.6-1 permits you to set a maximum request limit. If the limit is exceeded, the allocation is instead memory-mapped on disk. Here we limit the maximum memory request by policy:</p> 146<pre class="highlight"><code><policy domain="system" name="max-memory-request" value="256MiB"/> </code></pre> 147 148<p>As of ImageMagick version 7.0.4-23, you can limit the maximum number of images in a sequence. For example, to limit an image sequence to 64 frames, use:</p> 149<pre class="highlight"><code><policy domain="resource" name="list-length" value="64"/></code></pre> 150 151<p>You can verify your policy changes are in effect with this command:</p> 152 153<pre class="pre-scrollable">-> identify -list policy 154Path: ImageMagick/policy.xml 155 Policy: Resource 156 name: time 157 value: 120 158 Policy: Resource 159 name: throttle 160 value: 0 161 Policy: Resource 162 name: thread 163 value: 2 164 Policy: Resource 165 name: file 166 value: 768 167 Policy: Resource 168 name: disk 169 value: 1GiB 170 Policy: Resource 171 name: map 172 value: 512MiB 173 Policy: Resource 174 name: memory 175 value: 256MiB 176 Policy: Resource 177 name: area 178 value: 16KP 179 Policy: Resource 180 name: height 181 value: 8KP 182 Policy: Resource 183 name: width 184 value: 8KP 185 Policy: Resource 186 name: temporary-path 187 value: /tmp 188 Policy: System 189 name: precision 190 value: 6 191 Policy: Path 192 rights: None 193 pattern: @* 194 195Path: [built-in] 196 Policy: Undefined 197 rights: None</pre> 198<p>Notice the <code>Cache</code> policy is not listed due to the <code>stealth</code> property.</p> 199 200<p>As of ImageMagick 7.0.6-0, you can programmatically set the ImageMagick security policy with SetMagickSecurityPolicy() (MagickCore) or MagickSetSecurityPolicy() (MagickWand).</p> 201 202<p>As of ImageMagick version 7.0.8-11, you can set a module security policy. For example, to prevent Postscript or PDF interpretation, use:</p> 203<pre class="highlight"><code><policy domain="module" rights="none" pattern="{ps,pdf,xps}/></code></pre> 204 205<p>For additional details about resource limits and the policy configuration file, read <a href="resources.html">Resources</a> and <a href="architecture.html">Architecture</a>.</p> 206 207<h2><a class="anchor" id="synchronize"></a>Pixel Cache Synchronize Policy</h2> 208 209<p>When writing image pixels to disk, ImageMagick firsts preallocates the disk file, which is much faster than fully populating the file with zeros. To further increase performance, we memory-map the file on disk. With memory-mapping, we get an increase in performance (up to 5x), however, there remains a possibility that as the disk file is populated, it may run out of free space. The OS then throws a SIGBUS signal which prevents ImageMagick from continuing. To prevent a SIGBUS, use this security policy: 210 211<pre class="highlight"> 212<policy domain="cache" name="synchronize" value="True"/> 213</pre> 214 215<p>Set to True to ensure all image data is fully flushed and synchronized to disk. There is a performance penalty, however, the benefits include ensuring a valid image file in the event of a system crash and early reporting if there is not enough disk space for the image pixel cache.</p> 216 217<h2><a class="anchor" id="zero-configuration"></a>Zero Configuration Security Policy</h2> 218 219<p>A zero configuration build of ImageMagick does not permit external configuration files. To define your security policy, you must instead edit the <code>MagickCore/policy-private.h</code> source module, add your policy statements, and then build the ImageMagick distribution. Here is an example zero configuration security policy:</p> 220 221<pre class="highlight"><code>static const char 222 *ZeroConfigurationPolicy = \ 223"<policymap> \ 224 <policy domain=\"coder\" rights=\"none\" pattern=\"MVG\"/> \ 225</policymap>";</code></pre> 226 227<h2><a class="anchor" id="other"></a>Other Security Considerations</h2> 228 229<p>If you spot a security flaw in ImageMagick, post your concern as an issue to 230<a href="https://github.com/ImageMagick/ImageMagick/issues">GitHub</a>. Be sure to include how to reproduce the security flaw and a link to any images needed to reproduce the flaw. Alternatively, <a href="https://imagemagick.org/script/contact.php">contact us</a> and select Security Issue as the issue.</p> 231 232<p>In addition to the security policy, you can make ImageMagick safer by ...</p> 233<ul> 234<li>keeping ImageMagick up-to-date. The latest releases have fixes for any security flaws we discovered in the past;</li> 235<li>sanitizing any filenames or command line options you pass to ImageMagick;</li> 236<li>running ImageMagick in a sanitized software container such as Docker;</li> 237<li>running ImageMagick as the least-privileged user (e.g. 'nobody');</li> 238<li>explicitly setting the image file type. For example, use the filename <code>png:image.png</code> rather than <code>image.png</code>. Without an explicit image type in the filename, ImageMagick guesses the image type.</li> 239</ul> 240 241</div> 242 </div> 243 </main><!-- /.container --> 244 <footer class="magick-footer"> 245 <p><a href="security-policy.html">Security</a> • 246 <a href="architecture.html">Architecture</a> • 247 <a href="links.html">Related</a> • 248 <a href="sitemap.html">Sitemap</a> 249 250 <a href="security-policy.html#"><img class="d-inline" id="wand" alt="And Now a Touch of Magick" width="16" height="16" src="../images/wand.ico"/></a> 251 252 <a href="http://pgp.mit.edu/pks/lookup?op=get&search=0x89AB63D48277377A">Public Key</a> • 253 <a href="support.html">Donate</a> • 254 <a href="https://imagemagick.org/script/contact.php">Contact Us</a> 255 <br/> 256 <small>© 1999-2019 ImageMagick Studio LLC</small></p> 257 </footer> 258 259 <!-- Javascript assets --> 260 <script src="assets/magick.js" crossorigin="anonymous"></script> 261 <script>window.jQuery || document.write('<script src="https://localhost/ajax/libs/jquery/3.3.1/jquery.min.js"><\/script>')</script> 262</body> 263</html> 264<!-- Magick Cache 5th January 2019 11:42 -->
