{"id":13754,"date":"2017-08-28T08:00:11","date_gmt":"2017-08-28T13:00:11","guid":{"rendered":"https:\/\/www.psafe.com\/en\/blog\/?p=13754"},"modified":"2018-06-28T17:05:01","modified_gmt":"2018-06-28T21:05:01","slug":"what-is-the-yahoobleed-bug-and-how-it-affects-you","status":"publish","type":"post","link":"https:\/\/www.psafe.com\/en\/blog\/what-is-the-yahoobleed-bug-and-how-it-affects-you\/","title":{"rendered":"What is the ‘Yahoobleed’ Bug and How It Affects You"},"content":{"rendered":"

Because many malicious online attacks occur using content that mimics familiar companies and their content, it\u2019s best to run a full virus scan after downloading any files from the Internet or from your email. Click below to run check your phone for malware:<\/span><\/p>\n

\"run-security-scan\"<\/a>
<\/center><\/center>
\nA complete scan effectively checks every inch of your device for any malware or security breaches to avoid a loss of personal information.<\/span><\/p>\n

What is Yahoobleed?
\n<\/b>Chris Evans, a security expert, discovered two crucial vulnerabilities in Yahoo\u2019s image processing library earlier this year that put Yahoo users at serious risk of a security breach. The vulnerabilities discovered by Evans have been aptly named \u201cYahoobleed,\u201d in reference to the resulting leak of information that can be exploited by a malicious attacker. Caused by Yahoo’s negligence and an error in the code, the two issues were directly related to ImageMagick, which is used by Yahoo to condense, convert, and store large image files sent via email.<\/span><\/p>\n

Read More: <\/b>Tips for Detecting and Avoiding Spam Emails<\/b><\/a><\/p>\n

Shockingly, one of these serious bugs could have easily been avoided had Yahoo updated their version of ImageMagick in 2015 when the company released a new patch to prevent the error. Evans tested his theories on Yahoo\u2019s security by sending himself a malicious email attachment. After opening the file, he discovered that if an attacker employed a similar technique, he could receive access to other private email attachments as well as sensitive information stored in the server memory. If a Yahoo email user opened one of these malicious attachments, it would result in the namesake leak of information to the end user, the attacker.<\/p>\n

After Evans discovered the second vulnerability, Yahoo made the decision to halt the use of ImageMagick in an attempt to prevent any further breaches of security. Although many commend Yahoo for their decision, these vulnerabilities are not uncommon and still pose a serious threat. At this time, the company believes the issue has been resolved.<\/span><\/p>\n

How to Protect Yourself Online
\n<\/b>While Yahoo may no longer have an issue with \u201cYahoobleed,\u201d the recent vulnerabilities should be a reminder that even trusted institutions like Yahoo are subject to attack. Basic best practices in preventing a leak of personal information should include selective engagement with spam emails and regular virus scanning. First and foremost, do not open an email or an email attachment from a sender that you do not recognize or that looks potentially malicious. If the email appears to be from a familiar sender but is asking for new information or using a heightened sense of urgency that is inconsistent with their typical email content, do not click on any links or download attachments.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

One security expert discovered that opening a simple email attachment could lead to a massive leak in secure information. Find out how you can protect yourself.<\/p>\n","protected":false},"author":83,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","footnotes":""},"categories":[5],"tags":[1203,162,4328,259,182,218,358,223],"class_list":["post-13754","post","type-post","status-publish","format-standard","hentry","category-security","tag-android-phone","tag-antivirus","tag-antivirus-protection","tag-hackers","tag-malware","tag-privacy","tag-protection","tag-tips"],"_links":{"self":[{"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/posts\/13754","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/users\/83"}],"replies":[{"embeddable":true,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/comments?post=13754"}],"version-history":[{"count":2,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/posts\/13754\/revisions"}],"predecessor-version":[{"id":19086,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/posts\/13754\/revisions\/19086"}],"wp:attachment":[{"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/media?parent=13754"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/categories?post=13754"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.psafe.com\/en\/blog\/wp-json\/wp\/v2\/tags?post=13754"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}