<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic PLEASE READ: Important Message Regarding Security in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/please-read-important-message-regarding-security/m-p/230710#M183840</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;All-&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks to Jeff Potts at Metaversant ( &lt;/SPAN&gt;&lt;A href="http://www.metaversant.com" rel="nofollow noopener noreferrer"&gt;http://www.metaversant.com&lt;/A&gt;&lt;SPAN&gt;), Alfresco has become aware of a potential security loophole where the jBPM process deployer servlet runs without authentication. This means that a valid user may deploy a workflow that grants them admin access or similar. However, this loophole does require the user to have a valid account on the system and a good technical understanding of Alfresco.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Alfresco has identified a WAR file configuration change to eliminate this potential security loophole. Alfresco strongly recommends that you complete the following instructions for any 2.1, 2.2, and 3.x system to eliminate the risk.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;1. Create a backup directory and give it an appropriate name, such as &amp;lt;ALFRESCOBACKUP&amp;gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Copy your currently deployed alfresco.war file to this backup directory.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3. Create a new empty directory and unzip your backup alfresco. war file there.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;For Linux&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;a) mkdir ~/alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;b) cd ~/alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;c) jar xvf &amp;lt;ALFRESCOBACKUP&amp;gt;/alfresco.war&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For Windows&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;a) mkdir C:\alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;b) cd /D C:\alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;c) jar xvf &amp;lt;ALFRESCOBACKUP&amp;gt;/alfresco.war&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;4. In this new directory (~/alfresco), edit the WEB-INF/web.xml file to comment out the following lines.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Change:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;servlet-mapping&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;servlet-name&amp;gt;JBPMDeployProcessServlet&amp;lt;/servlet-name&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;url-pattern&amp;gt;/jbpm/deployprocess&amp;lt;/url-pattern&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;/servlet-mapping&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;To:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;!–servlet-mapping&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;servlet-name&amp;gt;JBPMDeployProcessServlet&amp;lt;/servlet-name&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;url-pattern&amp;gt;/jbpm/deployprocess&amp;lt;/url-pattern&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;/servlet-mapping–&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;5. Zip this directory to create a new alfresco.war.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;For Linux&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;a) cd ~/alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;b) jar cvf ../alfresco.war .&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For Windows&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;a) cd /D C:\alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;b) jar cvf ..\alfresco.war .&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;6. Deploy the new alfresco.war using the appropriate instructions for your application server.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;SPAN&gt;7. Confirm that accessing the URL &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://" rel="nofollow noopener noreferrer"&gt;http://&lt;/A&gt;&lt;SPAN&gt;&amp;lt;host:8080&amp;gt;/alfresco/jbpm/deployprocess returns a status 404 error.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Alfresco has applied this configuration to all hotfix branches, ensuring that all future patches and service packs include the change.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In Alfresco Version 3.3 SP3, you will be able to configure the JBPM process deployer servlet via alfresco-global.properties. Refer to the Alfresco Documentation on Network for more details post-release.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This solution has been verified against 3.3 SP1, 3.2 SP2, 2.2 SP8, and 2.1 SP7.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 23 Jul 2010 13:54:14 GMT</pubDate>
    <dc:creator>nancyg</dc:creator>
    <dc:date>2010-07-23T13:54:14Z</dc:date>
    <item>
      <title>PLEASE READ: Important Message Regarding Security</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/please-read-important-message-regarding-security/m-p/230710#M183840</link>
      <description>All-Thanks to Jeff Potts at Metaversant ( http://www.metaversant.com), Alfresco has become aware of a potential security loophole where the jBPM process deployer servlet runs without authentication. This means that a valid user may deploy a workflow that grants them admin access or similar. However,</description>
      <pubDate>Fri, 23 Jul 2010 13:54:14 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/please-read-important-message-regarding-security/m-p/230710#M183840</guid>
      <dc:creator>nancyg</dc:creator>
      <dc:date>2010-07-23T13:54:14Z</dc:date>
    </item>
    <item>
      <title>Re: PLEASE READ: Important Message Regarding Security</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/please-read-important-message-regarding-security/m-p/230711#M183841</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Another way to solve this security loophole is via an Apache HTTP server in front of the Alfresco installation (Tomcat).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;Location "/alfresco/jbpm/deployprocess" &amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Deny from all&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/Location&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I always install and configure a separate Apache server which connects to Alfresco on tomcat via mod_proxy_ajp (binary protocol). Normally I even disable the HTTP connector on port 8080. And I also configure Apache to serve the static files using Aliasses on the static directories.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ProxyPass /alfresco/images !&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ProxyPass /alfresco/css !&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ProxyPass /alfresco/scripts !&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ProxyPass /alfresco/swf !&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ProxyPass /alfresco/yui !&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ProxyPass /alfresco ajp://localhost:8009/alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ProxyPassReverse /alfresco ajp://localhost:8009/alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Alias /alfresco/images "/opt/alfresco/tomcat/webapps/alfresco/images"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Alias /alfresco/css "/opt/alfresco/tomcat/webapps/alfresco/css"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Alias /alfresco/scripts "/opt/alfresco/webapps/alfresco/scripts"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Alias /alfresco/swf "/opt/alfresco/webapps/alfresco/swf"&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Alias /alfresco/yui "/opt/alfresco/webapps/alfresco/yui"&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Advantages:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Tomcat does not have to serve static files. Apache does that a lot better and faster&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Use port 80 by default&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Using a rewrite rule, I can add /alfresco automatically.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- A lot more secure to offer your end users an Apache interface and keep the Tomcat interface including the management console separate. Only open port 80 (and 443) in the firewall.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- Very easy to implement SSL on Apache&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;…&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In short, just use a Web Server for what it's built and use the Application Server to serve the application, and nothing more.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Implementing this security fix took me only one minute and no restart of Alfresco was required. Even more, the Alfresco war is still original.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Aug 2010 12:28:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/please-read-important-message-regarding-security/m-p/230711#M183841</guid>
      <dc:creator>heydenb</dc:creator>
      <dc:date>2010-08-04T12:28:23Z</dc:date>
    </item>
  </channel>
</rss>

