{"id":25445,"date":"2023-03-27T20:09:07","date_gmt":"2023-03-27T14:39:07","guid":{"rendered":"https:\/\/www.kaspersky.co.in\/blog\/windows-11-google-pixel-image-editing-bug\/25445\/"},"modified":"2023-03-27T20:09:19","modified_gmt":"2023-03-27T14:39:19","slug":"windows-11-google-pixel-image-editing-bug","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.in\/blog\/windows-11-google-pixel-image-editing-bug\/25445\/","title":{"rendered":"The secret&#8217;s out: cropped and edited pictures can be restored"},"content":{"rendered":"<p>You might think that hiding sensitive information in a picture is a cakewalk. Just blot out your secrets with a big black marker in any image editor. Or even better: just crop the bit of the photo or screenshot that contains your personal data. What could possibly go wrong?<\/p>\n<p>Quite a lot, in fact. We\u2019ve already posted about <a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-leak-image-info\/34875\/\" target=\"_blank\" rel=\"noopener nofollow\">how not to hide information in images<\/a> and <a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-leak-info-from-docs\/37362\/\" target=\"_blank\" rel=\"noopener nofollow\">how not to retouch pictures embedded in documents<\/a>. But a recent study shows that you can still come a cropper, so to speak, even if you take just about every conceivable precaution\u00a0\u2014 and all due to a bug related to image processing. Let\u2019s take a closer look at how two standard image-editing tools \u2014 one on Google Pixel and the other in Windows\u00a011 \u2014 can reveal supposedly hidden information in images.\n<\/p>\n<h2>How to recover hidden information in screenshots edited on Google Pixel<\/h2>\n<p>\nIt all started when security researchers <a href=\"https:\/\/twitter.com\/ItsSimonTime\" target=\"_blank\" rel=\"nofollow noopener\">Simon Aarons<\/a> and <a href=\"https:\/\/twitter.com\/David3141593\" target=\"_blank\" rel=\"nofollow noopener\">David Buchanan<\/a> discovered a vulnerability they named <a href=\"https:\/\/twitter.com\/ItsSimonTime\/status\/1636857478263750656\" target=\"_blank\" rel=\"nofollow noopener\">Acropalypse<\/a>: it turns out that Markup, the Google Pixel built-in image editor, saves edited PNG files in a way that lets them be fully or partially recovered.<\/p>\n<p>When processing PNG images, instead of saving a completely new PNG file, Markup overwrites the old one in a very peculiar way. If you crop a picture, its size in bytes compared to the original decreases, of course. The same thing happens if you paint over part of an image with a single color\u00a0\u2014 thanks to the compression algorithms that are very good at packing solid-colored areas. But the file saved after editing in Markup has the same size as the original: the app simply overwrites the new data on top of the old, leaving a \u201ctail\u201d of the initial image data in the file. And with the help of a tool created by the researchers (<a href=\"https:\/\/acropalypse.app\/\" target=\"_blank\" rel=\"nofollow noopener\">available online<\/a>), it\u2019s possible to partially restore the original.<\/p>\n<p>Here\u2019s how the researchers themselves illustrate what\u2019s going on:<\/p>\n<div id=\"attachment_47654\" style=\"width: 2058px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2023\/03\/27200817\/windows-11-google-pixel-image-editing-bug-01.png\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-47654\" class=\"size-full wp-image-47654\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2023\/03\/27200817\/windows-11-google-pixel-image-editing-bug-01.png\" alt=\"Illustration of the concept behind the Acropalypse vulnerability\" width=\"2048\" height=\"1152\"><\/a><p id=\"caption-attachment-47654\" class=\"wp-caption-text\">Recovery of an image edited with Google Pixel Markup. <a href=\"https:\/\/twitter.com\/ItsSimonTime\/status\/1636857478263750656\" target=\"_blank\" rel=\"nofollow noopener\">Source<\/a><\/p><\/div>\n<p>Note, though, that the screenshot used as the example here is both <em>redacted AND cropped<\/em>. Thus, importantly, the resulting image is significantly smaller than the original. After the edited version is saved on top of the original, there\u2019s a lot of non-overwritten data at the end of the file that can be recovered. And the fully unrestored or badly-restored area\u00a0\u2014 the top third of the resulting picture\u00a0\u2014 just so happens to contain nothing important.<\/p>\n<p>So the researchers\u2019 demonstration should be taken as an ideal case: in real life, the success of the tool will almost certainly be lower, and the result will largely depend on the circumstances. But that doesn\u2019t mean the problem can be ignored\u00a0\u2014 this vulnerability is nothing if not very unpleasant.<\/p>\n<p>It affects the following Google smartphones (highlighted are models that are no longer supported and will probably not get updates):\n<\/p>\n<ul>\n<li>Google Pixel <strong>3, 3 XL, 3a, 3a XL<\/strong>\n<\/li>\n<li>Google Pixel <strong>4, 4 XL, 4a,<\/strong> 4a(5G)<\/li>\n<li>Google Pixel 5, 5a<\/li>\n<li>Google Pixel 6, 6 Pro, 6a<\/li>\n<li>Google Pixel 7, 7 Pro<\/li>\n<\/ul>\n<p>\nIn addition to its colloquial name, Acropalypse, the vulnerability was designated CVE-2023-21036. It has already been patched in the <a href=\"https:\/\/source.android.com\/docs\/security\/bulletin\/pixel\/2023-03-01\" target=\"_blank\" rel=\"nofollow noopener\">March Android update for the Pixel smartphones<\/a>. Alas, the update is powerless to fix old edited screenshots that have already been published or otherwise shared.\n<\/p>\n<h2>How to recover hidden information in screenshots edited in Windows 11<\/h2>\n<p>\nAfter Aarons and Buchanan posted their findings on Twitter, other researchers took up the cause. Logically assuming that other image-editing tools might use the same flawed mechanism for overwriting PNG files, they began to look for new vulnerable applications. And they found them, of course: a similar bug was <a href=\"https:\/\/twitter.com\/David3141593\/status\/1638222624084951040\" target=\"_blank\" rel=\"nofollow noopener\">detected<\/a> in Snipping Tool, a screenshot utility in Windows\u00a011.<\/p>\n<p>Windows\u00a011 Snipping Tool has exactly the same problem: the app overwrites edited PNG files on top of the original, and when the new file is smaller, some data from the original remains at the end of the file, from which the uncut image can be partially reconstructed.<\/p>\n<p>See <a href=\"https:\/\/www.bleepingcomputer.com\/news\/microsoft\/windows-11-snipping-tool-privacy-bug-exposes-cropped-image-content\/\" target=\"_blank\" rel=\"nofollow noopener\">this article on BleepingComputer<\/a> for more details:<\/p>\n<div id=\"attachment_47653\" style=\"width: 1258px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2023\/03\/27200854\/windows-11-google-pixel-image-editing-bug-02.jpg\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-47653\" class=\"size-full wp-image-47653\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/36\/2023\/03\/27200854\/windows-11-google-pixel-image-editing-bug-02.jpg\" alt=\"Acropalypse vulnerability in Windows 11 Snipping Tool\" width=\"1248\" height=\"2079\"><\/a><p id=\"caption-attachment-47653\" class=\"wp-caption-text\">Recovery of an image edited with Windows 11 Snipping Tool. <a href=\"https:\/\/www.bleepingcomputer.com\/news\/microsoft\/windows-11-snipping-tool-privacy-bug-exposes-cropped-image-content\/\" target=\"_blank\" rel=\"nofollow noopener\">Source<\/a><\/p><\/div>\n<p>Although in this case a smaller part of the original image was restored, the result is still impressive. Note that the problem seems to be confined only to Snipping Tool and only to the Windows 11 version. So users of earlier versions of Windows, or those who prefer to edit screenshots in Paint or a full-fledged graphics editor like Photoshop, aren\u2019t affected.<\/p>\n<p>The vulnerability in Windows\u00a011 Snipping Tool remains unclosed. But, again, even when an update arrives, it won\u2019t fix the problem with screenshots that are already out there.\n<\/p>\n<h2>What to do?<\/h2>\n<p>\nIf you use Windows\u00a011 Snipping Tool, or have a Google Pixel smartphone (gen 3\u20137), and you\u2019ve posted cropped or edited screenshots with passwords somewhere, consider those passwords compromised: change them immediately. Sure, you might struggle to remember every such instance, and in any case there\u2019s nothing much you can do about it: there do exist <a href=\"https:\/\/github.com\/infobyte\/CVE-2023-21036\" target=\"_blank\" rel=\"nofollow noopener\">Python scripts and YARA rules<\/a> for finding and treating such PNG images, but these are only for techies.<\/p>\n<p>On a final note, here are some tips on how to safely retouch images with sensitive data that you plan to post online or send to someone you don\u2019t know if you can fully trust:\n<\/p>\n<ul>\n<li>If you prefer to hide your secrets by painting over them or filling the area with solid color, make sure that the opacity is set to 100%.<\/li>\n<li>If you opt for pixelating or smearing, bear in mind that this operation is <a href=\"https:\/\/thehackernews.com\/2022\/02\/this-new-tool-can-retrieve-pixelated.html\" target=\"_blank\" rel=\"nofollow noopener\">reversible<\/a>.<\/li>\n<li>If you\u2019re cropping, save the image to a new file\u00a0\u2014 preferably using Photoshop\u2019s Save for Web tool or an equivalent: such a tool will definitely slice off the unwanted part of the file for the sake of optimization.<\/li>\n<\/ul>\n<p>\nLastly, before posting a picture that could spill a bean or two, ask yourself: is posting it really necessary?<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"premium-generic\">\n","protected":false},"excerpt":{"rendered":"<p>Do you edit images in Windows 11 or on Google Pixel? Due to a developer error, hidden information in cropped or edited pictures can be recovered.<\/p>\n","protected":false},"author":2726,"featured_media":25447,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1855,2196,9],"tags":[2925,363,43,1898,3109],"class_list":{"0":"post-25445","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-privacy","8":"category-threats","9":"category-tips","10":"tag-images","11":"tag-personal-data","12":"tag-privacy","13":"tag-tips","14":"tag-windows-11"},"hreflang":[{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/windows-11-google-pixel-image-editing-bug\/25445\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/windows-11-google-pixel-image-editing-bug\/20880\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/windows-11-google-pixel-image-editing-bug\/28050\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/windows-11-google-pixel-image-editing-bug\/25742\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/windows-11-google-pixel-image-editing-bug\/26131\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/windows-11-google-pixel-image-editing-bug\/28587\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/windows-11-google-pixel-image-editing-bug\/34932\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/windows-11-google-pixel-image-editing-bug\/47650\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/windows-11-google-pixel-image-editing-bug\/20369\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/windows-11-google-pixel-image-editing-bug\/20992\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/windows-11-google-pixel-image-editing-bug\/29952\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/windows-11-google-pixel-image-editing-bug\/26046\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/windows-11-google-pixel-image-editing-bug\/31759\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/windows-11-google-pixel-image-editing-bug\/31446\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.in\/blog\/tag\/privacy\/","name":"privacy"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/25445","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/users\/2726"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/comments?post=25445"}],"version-history":[{"count":1,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/25445\/revisions"}],"predecessor-version":[{"id":25446,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/posts\/25445\/revisions\/25446"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media\/25447"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/media?parent=25445"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/categories?post=25445"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.in\/blog\/wp-json\/wp\/v2\/tags?post=25445"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}