<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Adobe Product Security Incident Response Team (PSIRT)</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/" />
    <link rel="self" type="application/atom+xml" href="http://blogs.adobe.com/psirt/atom.xml" />
   <id>tag:blogs.adobe.com,2008:/psirt/176</id>
    <link rel="service.post" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176" title="Adobe Product Security Incident Response Team (PSIRT)" />
    <updated>2008-09-02T20:16:16Z</updated>
    <subtitle>Working to help protect customers from vulnerabilities in Adobe software</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.2</generator>
 
<entry>
    <title>Security Advisory - Flash Media Server</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/09/security_advisory_flash_media.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=7253" title="Security Advisory - Flash Media Server" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.7253</id>
    
    <published>2008-09-02T19:31:16Z</published>
    <updated>2008-09-02T20:16:16Z</updated>
    
    <summary>A new Security Advisory for Flash Media Server 3.0 has just been posted. This Advisory points customers to a recent tech note that describes how to protect Flash Media Server video content from stream capture software, or ‘rippers’....</summary>
    <author>
        <name>David Lenoe</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>A new <a href="http://www.adobe.com/go/apsa08-06">Security Advisory for Flash Media Server 3.0</a> has just been posted. This Advisory points customers to a <a href="http://www.adobe.com/go/kb405456">recent tech note</a> that describes how to protect Flash Media Server video content from stream capture software, or ‘rippers’.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Clipboard attack</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/08/clipboard_attack.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=6953" title="Clipboard attack" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.6953</id>
    
    <published>2008-08-20T00:44:38Z</published>
    <updated>2008-08-20T04:15:34Z</updated>
    
    <summary>We are aware of recent press reports about a potential “Clipboard attack” issue that involves Flash Player. Adobe is currently investigating potential solutions to this issue and will update customers as soon as we have more information to provide. This...</summary>
    <author>
        <name>David Lenoe</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>We are aware of recent press reports about a potential “Clipboard attack” issue that involves Flash Player. Adobe is currently investigating potential solutions to this issue and will update customers as soon as we have more information to provide.</p>

<p><strong>This posting is provided “AS IS” with no warranties and confers no rights</strong></p>]]>
        
    </content>
</entry>
<entry>
    <title>Security Bulletin - Presenter</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/08/security_bulletin_presenter.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=6865" title="Security Bulletin - Presenter" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.6865</id>
    
    <published>2008-08-08T21:23:18Z</published>
    <updated>2008-08-09T00:36:04Z</updated>
    
    <summary>We have just released a Security Bulletin and update for Presenter to resolve potential cross-site scripting issues in content generated by Presenter. In addition to updating Presenter installations, customers may need to update any content previously deployed on their websites....</summary>
    <author>
        <name>David Lenoe</name>
        
    </author>
            <category term="Security Bulletins and Advisories" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>We have just released a <a href="http://www.adobe.com/go/apsb08-17/">Security Bulletin and update for Presenter</a> to resolve potential cross-site scripting issues in content generated by Presenter. In addition to updating Presenter installations, customers may need to update any content previously deployed on their websites. Presenter 7 customers can update any deployed instances of viewer.swf and loadflash.js with the new files installed with the update. Presenter 6 customers will need to be more careful, as the new viewer.swf file may be incompatible with Presenter 6 content – so content may need to be re-generated.</p>

<p><strong>This posting is provided “AS IS” with no warranties and confers no rights</strong></p>]]>
        
    </content>
</entry>
<entry>
    <title>Verifying Installers</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/08/verifying_installers.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=6808" title="Verifying Installers" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.6808</id>
    
    <published>2008-08-04T19:26:50Z</published>
    <updated>2008-08-04T19:34:58Z</updated>
    
    <summary>We have seen coverage from the security community of a worm on popular social networking sites that is using social engineering lures to get users to install a piece of malware. According to the reports, the worm posts comments on...</summary>
    <author>
        <name>David Lenoe</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>We have seen coverage from the security community of a worm on popular social networking sites that is using social engineering lures to get users to install a piece of malware. According to the reports, the worm posts comments on these sites that include links to a fake site. If the link is followed, users are told they need to update their Flash Player. The installer, posted on a malicious site, of course installs malware instead of Flash Player.</p>

<p>We’d like to take this opportunity to reiterate the importance of validating installers and updates before installing them. First off, do not download Flash Player from a site other than adobe.com – you can find the link for downloading Flash Player <a href="http://www.adobe.com/go/getflashplayer/">here</a>. This goes for any piece of software (Reader, Windows Media Player, Quicktime, etc.) – if you get a notice to update, it’s not a bad idea to go directly to the site of the software vendor and download the update directly from the source. If the download is from an unfamiliar URL or an IP address, you should be suspicious. </p>

<p>Second, all Adobe software for Windows is signed with a digital certificate that is validated by Windows when you install our software. The Publisher will always be ‘Adobe Systems, Incorporated’, and you can verify this when you double-click the installer, or by right-clicking on the installer, selecting ‘Properties’, and going to the ‘Digital Signatures’ tab.</p>

<p>For Flash Player in particular, you can always go to <a href="http://www.adobe.com/products/flash/about/">this page</a> to verify what version of Flash Player you have installed, and what the current version of Flash Player is for your Operating System. The current Flash Player version is 9.0.124.0.</p>

<p><strong>This posting is provided “AS IS” with no warranties and confers no rights</strong><br />
</p>]]>
        
    </content>
</entry>
<entry>
    <title>Security Bulletin - RoboHelp Server</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/07/security_bulletin_robohelp_ser.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=6555" title="Security Bulletin - RoboHelp Server" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.6555</id>
    
    <published>2008-07-08T21:30:29Z</published>
    <updated>2008-07-08T21:32:32Z</updated>
    
    <summary>Our Security Bulletin release today is for RoboHelp Server (versions 6 and 7), along with an update to resolve a cross-site scripting issue. The issue does not affect the RoboHelp desktop versions, just the RoboHelp Server product. Please see the...</summary>
    <author>
        <name>David Lenoe</name>
        
    </author>
            <category term="Security Bulletins and Advisories" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>Our Security Bulletin release today is for <a href="http://www.adobe.com/go/apsb08-16">RoboHelp Server (versions 6 and 7)</a>, along with an update to resolve a cross-site scripting issue. The issue does not affect the RoboHelp desktop versions, just the RoboHelp Server product. Please <a href="http://www.adobe.com/go/apsb08-16">see the Bulletin</a> for more information.</p>

<p><strong>This posting is provided “AS IS” with no warranties and confers no rights</strong><br />
</p>]]>
        
    </content>
</entry>
<entry>
    <title>Security Bulletin - Reader and Acrobat</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/06/security_bulletin_reader_and_a.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=6429" title="Security Bulletin - Reader and Acrobat" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.6429</id>
    
    <published>2008-06-24T01:01:51Z</published>
    <updated>2008-06-24T04:03:36Z</updated>
    
    <summary>We’ve just released a Security Bulletin for Reader and Acrobat 8.1.2, along with an update to resolve a critical issue. This issue does not affect Reader 7.1.0 or Acrobat 7.1.0, or the upcoming Acrobat 9 and Reader 9 releases (expected...</summary>
    <author>
        <name>David Lenoe</name>
        
    </author>
            <category term="Security Bulletins and Advisories" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>We’ve just released a <a href="http://www.adobe.com/go/apsb08-15">Security Bulletin for Reader and Acrobat 8.1.2</a>, along with an update to resolve a critical issue. This issue does not affect Reader 7.1.0 or Acrobat 7.1.0, or the upcoming Acrobat 9 and Reader 9 releases (expected to be available by July).  All customers with Reader 8.1.2 and Acrobat 8.1.2 are strongly encouraged to <a href="http://www.adobe.com/go/apsb08-15">update to Reader or Acrobat 8.1.2 Security Update 1</a>. Acrobat 7 and Reader 7 users should <a href="http://www.adobe.com/go/apsb08-15">update to Acrobat 7.1.0 or Reader 7.1.0</a> if they haven't already.</p>

<p><strong>This posting is provided “AS IS” with no warranties and confers no rights</strong><br />
</p>]]>
        
    </content>
</entry>
<entry>
    <title>Security Bulletin – June 2008</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/06/security_bulletin_june_2008.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=6385" title="Security Bulletin – June 2008" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.6385</id>
    
    <published>2008-06-17T21:23:46Z</published>
    <updated>2008-06-17T21:31:49Z</updated>
    
    <summary>We’ve just released a Security Bulletin for Flex 3 along with an update to resolve a cross-site scripting issue. This bulletin affects History Management in Flex 3 SDK and Flex Builder 3. Please note that developers who use History Management...</summary>
    <author>
        <name>Erick Lee</name>
        
    </author>
            <category term="Security Bulletins and Advisories" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>We’ve just released a <a href="http://www.adobe.com/go/apsb08-14">Security Bulletin for Flex 3</a> along with an update to resolve a cross-site scripting issue. This bulletin affects History Management in Flex 3 SDK and Flex Builder 3. Please note that developers who use History Management will need to update their product installations as well as any already-deployed applications built with Flex 3. As noted in the bulletin, Flex 2 and Flex 2 content are not affected.</p>

<p>This posting is provided “AS IS” with no warranties and confers no rights<br />
</p>]]>
        
    </content>
</entry>
<entry>
    <title>More information on recent Flash Player exploit</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/05/more_information_on_recent_fla.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=6040" title="More information on recent Flash Player exploit" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.6040</id>
    
    <published>2008-05-30T00:28:26Z</published>
    <updated>2008-06-03T23:49:01Z</updated>
    
    <summary>Here’s some more information about the recent reports of Flash Player exploits in the wild that may help answer some of the questions we’ve been seeing: - This is not a zero-day exploit. Despite various reports that have been circulating,...</summary>
    <author>
        <name>David Lenoe</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>Here’s some more information about the recent reports of Flash Player exploits in the wild that may help answer some of the questions we’ve been seeing:</p>

<p>- This is not a zero-day exploit. Despite various reports that have been circulating, the Flash Player Standalone 9.0.124.0 and Linux Player 9.0.124.0 are NOT vulnerable to the exploits discussed in conjunction with the previously disclosed vulnerability Symantec posted on 5/27/08. Symantec originally believed this to be a zero-day, unpatched vulnerability, but as their latest update on their <a href="http://www.symantec.com/security_response/threatcon/index.jsp">Threatcon page</a> indicates, they have now confirmed this issue does not affect any versions of Flash Player 9.0.124.0.</p>

<p>- Although the original vulnerability, disclosed last month in <a href="http://www.adobe.com/go/apsb08-11">Security Bulletin APSB08-11</a>, affects all platforms (Mac, Windows, and Linux), all of the exploits we’ve seen so far target Windows users.  </p>

<p>- The ‘campaign’ included SQL injection attacks and apparently took advantage of various other (non-Flash Player) vulnerabilities to redirect users from legitimate sites to malicious domains serving the exploit SWFs.  </p>

<p>- Symantec and other major antivirus vendors have added detections for the exploits seen so far.</p>

<p> - The recent Flash Player 10 beta is also not vulnerable to this exploit.</p>

<p>Finally, at the risk of sounding repetitive, in order to make sure users are not vulnerable to these exploits, we strongly encourage users to download and <a href="http://www.adobe.com/go/getflashplayer">install the latest Flash Player update, 9.0.124.0</a>. No uninstall is necessary, just install the latest Flash Player. Customers using multiple browsers should perform the update for each browser installed on their system.</p>

<p></p>

<p><br />
</p>]]>
        
    </content>
</entry>
<entry>
    <title>Potential Flash Player issue - update</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/05/potential_flash_player_issue_u_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=6010" title="Potential Flash Player issue - update" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.6010</id>
    
    <published>2008-05-28T19:09:20Z</published>
    <updated>2008-05-29T02:26:53Z</updated>
    
    <summary>Here’s an update on our progress investigating the recent reports of a potential Flash Player exploit in the wild. The exploit appears to be taking advantage of a known vulnerability, reported by Mark Dowd of the ISS X-Force and wushi...</summary>
    <author>
        <name>David Lenoe</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>Here’s an update on our progress investigating the recent reports of a potential Flash Player exploit in the wild. The exploit appears to be taking advantage of a known vulnerability, <a href="http://www.adobe.com/go/apsb08-11">reported by Mark Dowd of the ISS X-Force and wushi of team509, that was resolved in Flash Player 9.0.124.0 </a>(CVE-2007-0071). This exploit does NOT appear to include a new, unpatched vulnerability as has been reported elsewhere – customers with Flash Player 9.0.124.0 should not be vulnerable to this exploit. We’re still looking in to the exploit files, and will update everyone with further information as we get it, but for now, we strongly encourage <a href="http://www.adobe.com/go/getflashplayer">everyone to download and install the latest Flash Player update, 9.0.124.0</a>.</p>

<p><strong>UPDATE:</strong> We've just gotten confirmation from Symantec that all versions of Flash Player 9.0.124.0 are not vulnerable to these exploits. Again, we strongly encourage <a href="http://www.adobe.com/go/getflashplayer">everyone to download and install the latest Flash Player update, 9.0.124.0</a>. To verify the Adobe Flash Player version number, access the <a href="http://www.adobe.com/products/flash/about/">About Flash Player page</a>, or right-click on Flash content and select “About Adobe (or Macromedia) Flash Player” from the menu. <strong>Customers using multiple browsers are advised to perform the check for each browser installed on their system and update if necessary.</strong></p>

<p>Thanks to Symantec for working very closely with us over the last 2 days to confirm that this is not a zero-day issue, and to Mark Dowd and wushi for originally reporting this issue. </p>

<p><strong>This posting is provided “AS IS” with no warranties and confers no rights</strong></p>]]>
        
    </content>
</entry>
<entry>
    <title>Potential Flash Player issue</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/05/potential_flash_player_issue.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=5999" title="Potential Flash Player issue" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.5999</id>
    
    <published>2008-05-27T19:05:28Z</published>
    <updated>2008-05-29T00:31:36Z</updated>
    
    <summary>Just a quick note to say we are aware of today’s report of a potential exploit involving Flash Player in the wild. We are working with Symantec to investigate the potential SWF vulnerability, and will have an update once we...</summary>
    <author>
        <name>David Lenoe</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>Just a quick note to say we are aware of <a href="http://www.securityfocus.com/bid/29386">today’s report of a potential exploit involving Flash Player in the wild</a>. We are working with Symantec to investigate the potential SWF vulnerability, and will have an update once we get more information.</p>

<p>UPDATE: This exploit appears to be taking advantage of a known vulnerability, <a href="http://www.adobe.com/go/apsb08-11">reported by Mark Dowd of the ISS X-Force and wushi of team509, that was resolved in Flash Player 9.0.124.0 </a>(CVE-2007-0071). We strongly encourage <a href="http://www.adobe.com/go/getflashplayer">everyone to download and install the latest Flash Player update, 9.0.124.0</a>.</p>

<p><strong>This posting is provided “AS IS” with no warranties and confers no rights</strong></p>]]>
        
    </content>
</entry>
<entry>
    <title>Security Bulletins - May 2008</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/05/security_bulletins_may_2008.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=5826" title="Security Bulletins - May 2008" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.5826</id>
    
    <published>2008-05-07T01:59:43Z</published>
    <updated>2008-05-07T06:06:20Z</updated>
    
    <summary>We have just released an important update for Acrobat 7 and Adobe Reader 7 users, which resolves the issues previously mentioned in Security Advisory APSA08-01. If you have already updated to Reader 8.1.2 or Acrobat 8.1.2, you are all set....</summary>
    <author>
        <name>David Lenoe</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>We have just released an <a href="http://www.adobe.com/support/security/bulletins/apsb08-13.html">important update for Acrobat 7 and Adobe Reader 7</a> users, which resolves the issues previously mentioned in <a href="http://www.adobe.com/go/apsa08-01">Security Advisory APSA08-01</a>. If you have already updated to Reader 8.1.2 or Acrobat 8.1.2, you are all set. But, if you are using Acrobat 7, or if you are using Adobe Reader 7 and can’t update to Reader 8, please review <a href="http://www.adobe.com/support/security/bulletins/apsb08-13.html">Security Bulletin APSB08-13</a> and update your installations accordingly. As previously mentioned, we have heard reports of one of the issues being exploited in the wild, so please update if you haven’t already.</p>

<p>Also note that we released <a href="http://www.adobe.com/support/security/advisories/apsa08-05.html">Security Advisory APSA08-05</a> for After Effects CS3 today, in response to a public posting of a BMP-handling vulnerability in After Effects. As mentioned in the advisory, it’s not a common workflow to use BMP files within After Effects, and most files used in the After Effects workflow come from trusted sources. That said, as always, we advise customers to exercise caution when receiving and opening files from untrusted sources.<br />
<strong><br />
This posting is provided “AS IS” with no warranties and confers no rights<br />
</strong></p>]]>
        
    </content>
</entry>
<entry>
    <title>Security Bulletins - April 2008</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/04/security_bulletins_april_2008_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=5578" title="Security Bulletins - April 2008" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.5578</id>
    
    <published>2008-04-08T23:58:19Z</published>
    <updated>2008-04-09T00:13:32Z</updated>
    
    <summary>We’ve just released two security bulletins – first and foremost, there’s a Flash Player update announced in APSB08-11 that provides solutions for previously disclosed vulnerabilities (including the PWN2OWN Contest issue reported by Shane Macaulay) in Flash Player version 9.0.115.0 and...</summary>
    <author>
        <name>David Lenoe</name>
        
    </author>
            <category term="Security Bulletins and Advisories" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>We’ve just released two security bulletins – first and foremost, there’s a Flash Player update announced in <a href="http://www.adobe.com/go/apsb08-11">APSB08-11</a> that provides solutions for previously disclosed vulnerabilities (including the PWN2OWN Contest issue reported by Shane Macaulay) in Flash Player version 9.0.115.0 and earlier, and 8.0.39.0 and earlier. This is the update we’ve referred to in a couple of earlier posts. These potential vulnerabilities could allow someone who successfully exploits them to take control of the affected system, so we recommend users update to the latest version of Flash Player (ideally 9.0.124.0) available for their operating system by downloading it from the <a href="http://www.adobe.com/go/getflashplayer">Player Download Center</a>.</p>

<p>There are also security enhancements that provide further mitigations for the previously disclosed DNS Rebinding (CVE-2007-5275), cross-domain policy file (CVE-2007-6243), and port-scanning (CVE-2007-4324) issues listed in <a href="http://www.adobe.com/go/apsb07-20">Security Bulletin APSB07-20</a> (originally posted on December 18, 2007) and the cross-site scripting issues (CVE-2007-6637) listed in <a href="http://www.adobe.com/go/apsa07-06">Security Advisory APSA07-06</a> (originally posted on December 23, 2007). Per our previous guidance about these potential issues, it’s recommended that content developers review <a href="http://www.adobe.com/devnet/flashplayer/articles/flash_player9_security_update.html">this Adobe Developer Center article</a> to determine if the security enhancements may affect their content, and begin implementing any necessary changes.</p>

<p>We’d like to thank all the researchers who reported the issues covered by this update – all the details are in the ‘Acknowledgments’ section, but we’d like to emphasize that we really appreciate the cooperation and help.</p>

<p>We also released a Security Bulletin for ColdFusion, <a href="http://www.adobe.com/go/apsb08-12">APSB08-12</a> that resolves a pretty basic bug in the remoting-config.xml file that controls the access level to CFC methods for Flex 2 Remoting.</p>

<p>*This posting is provided "AS IS" with no warranties, and confers no rights.*</p>]]>
        
    </content>
</entry>
<entry>
    <title>CanSecWest 2008 Pwn2Own Contest</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/04/cansecwest_2008_pwn2own_contes_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=5549" title="CanSecWest 2008 Pwn2Own Contest" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.5549</id>
    
    <published>2008-04-03T01:35:26Z</published>
    <updated>2008-04-03T01:48:32Z</updated>
    
    <summary>On Friday March 28, 2008 during the CanSecWest 2008 security conference Shane Macaulay of Security Objectives uncovered a potential security issue with Flash Player. Adobe Product Incident Response Team (PSIRT) received information regarding the exploit from TippingPoint, who sponsored the...</summary>
    <author>
        <name>Erick Lee</name>
        
    </author>
            <category term="Security Bulletins and Advisories" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>On Friday March 28, 2008 during the CanSecWest 2008 security conference Shane Macaulay of Security Objectives uncovered a potential security issue with Flash Player. Adobe Product Incident Response Team (PSIRT) received information regarding the exploit from TippingPoint, who sponsored the contest, on Friday evening. After some internal investigation, we found that via our ongoing response and security testing process we were aware of the issue and had fixed it for our security update coming in the next Flash Player update later this month. </p>

<p><strong>What should I do as a customer?</strong></p>

<p>We have fixed the issue and it will be in our next update coming later this month. Adobe is not aware of any active exploits in wild. The security researchers have reported the information to us responsibly giving the Flash Player team time to investigate and deliver a patch to you.  We will provide more information as it becomes available.</p>

<p>*This posting is provided "AS IS" with no warranties, and confers no rights.*</p>]]>
        
    </content>
</entry>
<entry>
    <title>Preparing for April Flash Player 9 Security Update</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/03/preparing_for_april_flash_play.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=5383" title="Preparing for April Flash Player 9 Security Update" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.5383</id>
    
    <published>2008-03-12T00:32:22Z</published>
    <updated>2008-03-12T00:34:09Z</updated>
    
    <summary>Quick note to let you know that we are giving advanced notice to our customers about some security enhancements in a security update to Flash Player scheduled for April 2008. This update may impact existing SWF content for some customers....</summary>
    <author>
        <name>David Lenoe</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>Quick note to let you know that we are giving advanced notice to our customers about some security enhancements in a security update to Flash Player scheduled for April 2008. This update may impact existing SWF content for some customers. The issues addressed are all previously disclosed – specifically, we’ll be providing further mitigations for the previously disclosed DNS Rebinding (CVE-2007-5275), cross-domain policy file (CVE-2007-6243), and port-scanning (CVE-2007-4324) issues listed in <a href="http://www.adobe.com/go/apsb07-20">Security Bulletin APSB07-20</a> (originally posted on December 18, 2007) and the cross-site scripting issues (CVE-2007-6637) listed in <a href="http://www.adobe.com/go/apsa08-06">Security Advisory APSA07-06</a> (originally posted on December 23, 2007)</p>

<p>Note that Flash Player end users won’t be affected – all they need to do is update their Flash Player once the update goes live. But, if customers have SWF content on their websites, we’re advising them to review the upcoming Flash Player updates as described in <a href="http://www.adobe.com/devnet/flashplayer/articles/flash_player9_security_update.html">this Adobe Developer Connection article</a> to determine if their content will be impacted, and to begin implementing any necessary changes before the update is released.<br />
 <br />
Customers for whom the following situations apply should read <a href="http://www.adobe.com/devnet/flashplayer/articles/flash_player9_security_update.html">the article</a> in detail: <br />
 - Use of sockets or XMLSockets, regardless of the domain the SWF is connecting to <br />
 - Use of addRequestHeader or URLRequest.requestHeaders in any network API call when sending or loading data cross-domain OR Provides access to content on remote domains as a web service provider <br />
 - Use of SWFs that are exported for Flash Player 7 (SWF7) or below that communicate with the hosting HTML by any means <br />
 - Use of “javascript:” through network APIs to communicate outside a SWF </p>

<p>There’s lots of info in the article, which also links to technotes with more details about how to make the changes.</p>

<p><strong>This posting is provided “AS IS” with no warranties and confers no rights</strong><br />
</p>]]>
        
    </content>
</entry>
<entry>
    <title>Security Bulletins - March 11, 2008</title>
    <link rel="alternate" type="text/html" href="http://blogs.adobe.com/psirt/2008/03/security_bulletins_march_11_20.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.adobe.com/cgi-bin/mt-atom.cgi/weblog/blog_id=176/entry_id=5382" title="Security Bulletins - March 11, 2008" />
    <id>tag:blogs.adobe.com,2008:/psirt//176.5382</id>
    
    <published>2008-03-11T23:04:58Z</published>
    <updated>2008-03-11T23:12:16Z</updated>
    
    <summary>It’s been a busy day around here. We’ve released 5 Security Bulletins today, as follows: - APSB08-06 - Update available for potential ColdFusion MX 7 and ColdFusion 8 Cross Site Scripting security issue This one is specific to IIS6 installations...</summary>
    <author>
        <name>David Lenoe</name>
        
    </author>
            <category term="Security Bulletins and Advisories" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.adobe.com/psirt/">
        <![CDATA[<p>It’s been a busy day around here. We’ve released 5 Security Bulletins today, as follows:</p>

<p>- <a href="http://www.adobe.com/go/apsb08-06">APSB08-06 </a>- Update available for potential ColdFusion MX 7 and ColdFusion 8 Cross Site Scripting security issue<br />
This one is specific to IIS6 installations of ColdFusion.<br />
 <br />
- <a href="http://www.adobe.com/go/apsb08-07">APSB08-07 </a>- Update available for ColdFusion MX 7 and ColdFusion 8 Cross-Site Scripting issue<br />
This issue only affects CF apps where the Application.cfm or Application.cfc contains the setEncoding function. <br />
 <br />
- <a href="http://www.adobe.com/go/apsb08-08">APSB08-08</a> - Update available for ColdFusion MX 7 and ColdFusion 8 logs invalid admin interface log-in attempts<br />
We’ve added functionality with this update to record failed admin log-in attempts in application.log</p>

<p>- <a href="http://www.adobe.com/go/apsb08-09">APSB08-09</a> - Update available to resolve critical vulnerabilities in Adobe Form Designer 5.0 and Adobe Advanced Form Client 5.0 Components<br />
These issues are in ActiveX controls shipped with Form Designer and Form Client 5.0</p>

<p>- <a href="http://www.adobe.com/go/apsb08-10">APSB08-10</a> - Update available for potential LiveCycle Workflow 6.2 Cross Site Scripting security issue<br />
We’re asking LiveCycle Workflow 6.2 customers to contact their support rep to get this update.<br />
 <br />
And this Security Advisory:<br />
- <a href="http://www.adobe.com/go/apsa08-02">APSA08-01</a> - Privilege escalation issue in Adobe Reader 8.1.2 for Unix<br />
We published this advisory in response to a recent SUSE update for this relatively minor issue.</p>

<p><strong>This posting is provided “AS IS” with no warranties and confers no rights</strong></p>

<p> </p>]]>
        
    </content>
</entry>

</feed> 

