Commentary

George Hulme
 

Adobe Flash Player Under Attack

Security researchers are warning that an in-the-wild exploit within the Adobe Flash Player has been planted in from 20,000 to 250,000 Web pages. If that wide range of potentially affected Web pages isn't enough disparity for you, try this on: it's not entirely clear what versions of Flash are at risk. Read on...

Security researchers are warning that an in-the-wild exploit within the Adobe Flash Player has been planted in from 20,000 to 250,000 Web pages. If that wide range of potentially affected Web pages isn't enough disparity for you, try this on: it's not entirely clear what versions of Flash are at risk. Read on...The attacks started from sites hosting the exploits (attack code) in China. But once these things get rolling, the front line spreads everywhere. First, if you're a Flash media player user, and haven't downloaded and applied the patch from Adobe released last month: Do so now. If you're not sure, check what version of Flash you're running (from the "About Flash") in each of your Firefox and Explorer browsers. I had to do this seven times this morning. The most recent version of Flash is available here.

Make sure you have version 9.0.124.0 or higher. (If you don't use Flash, go read Alex Wolfe's post on Joomia. Looks like really cool stuff.)


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

If you don't do these things, you run the risk of coming across a malicious SWF (Shockwave Flash) file, which could really happen from just about anywhere. That's one of the things that makes these types of attacks so risky. The attackers are currently attempting to install malware and Trojans on at-risk systems designed to pilfer passwords. But since these exploits are targeting a buffer overflow vulnerability (thanks for not checking your inputs, Mr. Adobe Developer), attackers could probably do whatever they so choose to your system. At first, researchers thought this was a zero-day attack; now they're leaning toward the possibility that these attacks are targeting a flaw discovered and detailed by Mark Dowd at IBM a few weeks back.

Symantec offers a rather convoluted analysis of the vulnerability and attacks to date here. For those not interested in deconstructing these sort of events, the takeaway is that Symantec advises disabling or uninstalling Flash until this mess is sorted out. They also mention setting a kill bit on CLSID d27cdb6e-ae6d-11cf-96b8-444553540000. But setting kill bits requires adult supervision, and I wouldn't advise doing this unless you really know what you're doing.

If you're a Firefox user, consider installing NoScript. It's perfect for days like this.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links