{"id":227291,"date":"2010-01-25T11:31:32","date_gmt":"2010-01-25T16:31:32","guid":{"rendered":"http:\/\/www.readwriteweb.com\/archives\/security_flaw_found_in_twitters_flash_widget.php"},"modified":"2010-01-25T11:31:32","modified_gmt":"2010-01-25T16:31:32","slug":"security-flaw-found-in-twitters-flash-widget","status":"publish","type":"post","link":"https:\/\/mereja.media\/index\/227291","title":{"rendered":"Security Flaw found in Twitter’s Flash Widget"},"content":{"rendered":"

A recently discovered security flaw in Twitter’s Flash-based website widget may have allowed attackers access to the login credentials of any Twitter user. According to Mike Bailey, an analyst at Foreground Security<\/a>, the problem involves a known vulnerability in Adobe’s Flash programming language, the language used to code the Twitter widget. In response, Twitter has disabled the widget in question<\/a> while they research the issue further. <\/p>\n

Sponsor<\/em>
<\/a><\/p>\n

Oddly enough, the vulnerability in question was initially discovered back in 2006, but many website operators have yet to address it says Bailey, according to a Reuters UK news story<\/a> about the potential Twitter security hole. After analyzing Twitter’s website, Bailey says the site may have been open to attack from hackers attempting to exploit this particular security hole for over a year. <\/p>\n

But the researcher doesn’t blame Adobe for the issue – the company informed programmers how to address the vulnerability years ago. Instead, this problem has to do with the “how the developers at Twitter, or whoever did this, built the Flash applications,” Bailey told a reporter at InternetNews.com<\/a>. <\/p>\n

According to a post<\/a> on the Twitter Status blog, the company has exercised “an abundance of caution” in disabling access to the widget as they have not yet heard about any accounts being affected by the reported vulnerability. However, says Bailey, there’s no way of know if any users were ever impacted by the issue and, if so, how many. “That is one of the big scary things; if they are being attacked, there is almost no way to find out short of a very close examination of the server logs or client logs, which generally aren’t stored,” he said<\/a>.<\/p>\n

This is by no means the first security issue for the microblogging startup. The company has seen everything from DNS hijacking<\/a> to the theft of corporate documents<\/a> and even fell victim to a distributed denial-of-service attack<\/a> which affected other social media properties on the web including LiveJournal and Facebook. Twitter users have also had their accounts hacked<\/a> and have had to deal with the constant threat of internet malware<\/a> posted to the site via shortened links. If anything, a news story about yet another Twitter security threat almost seems like a non-event these days, given how many issues the company has faced over the few short years they’ve been in operation. But considering current Twitter’s status as a piece of our modern-day’s communication infrastructure, it’s unnerving to hear about issues such as these…especially considering how this one in particular should have been addressed from the get-go. <\/p>\n

Discuss<\/a><\/strong><\/p>\n

<\/img><\/a>
\n<\/img><\/a><\/p>\n

\n<\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a>\n<\/div>\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

A recently discovered security flaw in Twitter’s Flash-based website widget may have allowed attackers access to the login credentials of any Twitter user. According to Mike Bailey, an analyst at Foreground Security, the problem involves a known vulnerability in Adobe’s Flash programming language, the language used to code the Twitter widget. In response, Twitter has […]<\/p>\n","protected":false},"author":2952,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-227291","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts\/227291","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/users\/2952"}],"replies":[{"embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/comments?post=227291"}],"version-history":[{"count":0,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts\/227291\/revisions"}],"wp:attachment":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/media?parent=227291"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/categories?post=227291"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/tags?post=227291"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}