According to the CVSS metric, successful exploitation of this vulnerability could lead to some loss of confidentiality (C:L)? What does that mean for this vulnerability? When an existing image is partially overwritten, an attacker may be able to recover parts of the original image through the use of a special tool. According to the CVSS metric, user interaction is required (UI:R). What interaction would the user have to do for this Low severity vulnerability? The severity of this vulnerability is Low because successful exploitation requires uncommon user interaction and several factors outside of an attacker's control. For an image to be subject to this issue, a user must have created it under specific conditions: The user must take a screenshot, save it to a file, modify the file (for example, crop it), and then save the modified file to the same location. The user must open an image in Snipping Tool, modify the file (for example, crop it), and then save the modified file to the same location. Common use cases like copying the image from Snipping Tool or modifying it before saving it are not affected. For example, if you take a screenshot of your bank statement, save it to your desktop, and crop out your account number before saving it to the same location, the cropped image could still contain your account number in a hidden format that could be recovered by someone who has access to the complete image file. However, if you copy the cropped image from Snipping Tool and paste it into an email or a document, the hidden data will not be copied, and your account number will be safe. What versions of Snipping Tool are affected? The default Snipping Tool in Windows 10 and older versions are unaffected. Only Snip & Sketch in Windows 10 and Snipping Tool in Windows 11 are affected by this vulnerability. A security update has been released for these applications, which is available through the Microsoft Store. How can I check if the update is installed? For Snip and
Maturity: Exploit
David Buchanan (@David3141593) <br> Chris Blume (@ProgramMax), Simon Aarons (@ItsSimonTime)