	
<rss version="2.0">
	<channel>
		<title>Dotcms Security Issues</title>
		<link>http://dotcms.com/security/</link>
        <description>RSS Feed for Security Issues in Dotcms</description>
									<item>
					<title>SessionID Visible to All Admins Via Logged Users Tab</title>
					<link>http://dotcms.com/security/SI-72</link>
					<guid>http://dotcms.com/security/SI-72</guid>
					<pubDate>Fri, 19 Apr 2024 13:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;In the &lt;span style=&quot;font-weight: 400;&quot;&gt;&lt;strong&gt;System &amp;rarr; Maintenance&lt;/strong&gt; tool, the Logged Users tab surfaces sessionId data for all users via the Direct Web Remoting API (&lt;span&gt;&lt;code&gt;UserSessionAjax.getSessionList.dwr&lt;/code&gt;) calls. While this ...]]></description>
				</item>
												<item>
					<title>HTML Injection Error on Password Reset Login Page</title>
					<link>http://dotcms.com/security/SI-71</link>
					<guid>http://dotcms.com/security/SI-71</guid>
					<pubDate>Mon, 8 Apr 2024 00:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt;The &quot;reset password&quot; login page accepted an HTML injection via URL parameters.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt;This has already been rectified via patch, and as such it cannot be demonstrated via Demo site link...]]></description>
				</item>
												<item>
					<title>Improper Handling of Database Credentials During Logging</title>
					<link>http://dotcms.com/security/SI-70</link>
					<guid>http://dotcms.com/security/SI-70</guid>
					<pubDate>Fri, 15 Mar 2024 01:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt;The username and password for PostgreSQL database connections appears in the log output visible in the &lt;strong&gt;System &amp;rarr; Maintenance&lt;/strong&gt; tool.&amp;nbsp; &lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt;OWASP Top ...]]></description>
				</item>
												<item>
					<title>Broken Access Control for Roles with User Admin</title>
					<link>http://dotcms.com/security/SI-69</link>
					<guid>http://dotcms.com/security/SI-69</guid>
					<pubDate>Fri, 15 Mar 2024 00:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt;The Tools and Log Files tabs under the &lt;strong&gt;System &amp;rarr; Maintenance&lt;/strong&gt; tool, which is and always has been an admin tool, are accessible to some without the CMS Admin role. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style=&quot;font-weight:...]]></description>
				</item>
												<item>
					<title>Broken Access Control &#8212; Normalization Filter</title>
					<link>http://dotcms.com/security/SI-68</link>
					<guid>http://dotcms.com/security/SI-68</guid>
					<pubDate>Fri, 30 Jun 2023 11:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;In dotCMS, the &lt;strong&gt;NormalizationFilter&lt;/strong&gt; is run on every request to strip invalid characters from incoming URLs. The default list of invalid characters to strip failed to include double slashes (&lt;code&gt;//&lt;/code&gt;), which allows a URL to be constructed...]]></description>
				</item>
												<item>
					<title>Directory Traversal with RCE</title>
					<link>http://dotcms.com/security/SI-67</link>
					<guid>http://dotcms.com/security/SI-67</guid>
					<pubDate>Thu, 15 Dec 2022 11:15:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;&lt;span&gt;An authenticated directory traversal vulnerability in dotCMS API&lt;/span&gt; can lead to RCE&lt;span&gt;.&amp;nbsp;&lt;/span&gt;A zip file at the &quot;&lt;em&gt;/api/integrity/_fixconflictsfromremote&lt;/em&gt;&quot; endpoint is accepted and extracted without performing path traversal check...]]></description>
				</item>
												<item>
					<title>Insecure random number generation in password reset token</title>
					<link>http://dotcms.com/security/SI-66</link>
					<guid>http://dotcms.com/security/SI-66</guid>
					<pubDate>Wed, 30 Nov 2022 00:00:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;dotCMS password reset token is generated using an insecure method &lt;em&gt;randomAlphanumeric()&amp;nbsp;&lt;/em&gt;which is not cryptographically secure and can be brute-forced. This may lead an attacker to gain access to admin account by requesting a password reset ...]]></description>
				</item>
												<item>
					<title>TempFileAPI can bypass access restrictions to access local/private network resources</title>
					<link>http://dotcms.com/security/SI-64</link>
					<guid>http://dotcms.com/security/SI-64</guid>
					<pubDate>Thu, 25 Aug 2022 09:30:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;dotCMS TempFileAPI allows a user to create a temporary files based on a passed in url - though dotCMS attempts to block any access to urls that contain local ips or private subnets. In resolving the remote url, the TempFileAPI follows any 302 redirects ...]]></description>
				</item>
												<item>
					<title>Possible DOS by overloading the TempFileResource</title>
					<link>http://dotcms.com/security/SI-65</link>
					<guid>http://dotcms.com/security/SI-65</guid>
					<pubDate>Wed, 17 Aug 2022 13:45:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;It is possible to call the TempFileResource multiple times, each time requesting the dotCMS server to download a large file. If done enough repeatedly, this will result in the Tomcat Request Thread pool to be exhausted and ultimately a denial of any other...]]></description>
				</item>
												<item>
					<title>Matrix URI parameters can expose private assets</title>
					<link>http://dotcms.com/security/SI-63</link>
					<guid>http://dotcms.com/security/SI-63</guid>
					<pubDate>Tue, 14 Jun 2022 13:45:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;Some Java Application frameworks, including those used by Spring or Tomcat, allow the use of &lt;a href=&quot;https://www.w3.org/DesignIssues/MatrixURIs.html&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;&amp;ldquo;matrix parameters&amp;rdquo;&lt;/a&gt; &amp;mdash; URI parameters separated by...]]></description>
				</item>
												<item>
					<title>Multipart File Directory Traversal can lead to remote execution</title>
					<link>http://dotcms.com/security/SI-62</link>
					<guid>http://dotcms.com/security/SI-62</guid>
					<pubDate>Mon, 28 Mar 2022 08:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;When files are uploaded into dotCMS via the content API, but before they become content, dotCMS writes the file down in a temp directory.&amp;nbsp; In the case of this vulnerability, dotCMS does not sanitize the filename passed in via the multipart request ...]]></description>
				</item>
												<item>
					<title>Log4j Zero-Day Exploit (CVE-2021-44228)</title>
					<link>http://dotcms.com/security/SI-61</link>
					<guid>http://dotcms.com/security/SI-61</guid>
					<pubDate>Mon, 20 Dec 2021 10:15:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;On Friday 12/10/2021, a critical vulnerability notification (&lt;a href=&quot;https://nvd.nist.gov/vuln/detail/CVE-2021-44228&quot;&gt;CVE-2021-44228&lt;/a&gt;) was released regarding a vulnerability in the log4j library, which is a very common open-source component used by ...]]></description>
				</item>
												<item>
					<title>Server-Side Request Forgery (SSRF) in dotcms/core</title>
					<link>http://dotcms.com/security/SI-60</link>
					<guid>http://dotcms.com/security/SI-60</guid>
					<pubDate>Tue, 14 Dec 2021 10:30:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;dotCMS TempFileAPI allows a SSRF that can allow to access to internal systems accessible via url&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;For example if dotCMS is connected to an unsecured elastisearch instance, this SSRF we can direct access the elastisearch REST API&lt;/li&gt;
&lt;li&gt;In ...]]></description>
				</item>
												<item>
					<title>Improper Privilege Management in Velocity</title>
					<link>http://dotcms.com/security/SI-59</link>
					<guid>http://dotcms.com/security/SI-59</guid>
					<pubDate>Mon, 13 Dec 2021 11:30:00 -0500</pubDate>
					<description><![CDATA[&lt;ol&gt;
&lt;li&gt;While editing a template we have total access to the User and UserModel classes via $user&lt;/li&gt;
&lt;li&gt;One of the UserModel methods is called setUserId&lt;/li&gt;
&lt;li&gt;If we call setUserId and pass &quot;system&quot; as parameter we get access to the system user role&lt;/li&gt;
&lt;li&gt;To...]]></description>
				</item>
												<item>
					<title>log4j2 JNDI Remote Expoit</title>
					<link>http://dotcms.com/security/SI-58</link>
					<guid>http://dotcms.com/security/SI-58</guid>
					<pubDate>Fri, 10 Dec 2021 08:30:00 -0500</pubDate>
					<description><![CDATA[&lt;div&gt;&lt;span&gt; &lt;/span&gt;&lt;/div&gt;
&lt;p&gt;&lt;span&gt;Like most enterprise java based systems, dotCMS relies on log4j2 for system logging.&amp;nbsp; &amp;nbsp;Apache Log4j2 &amp;lt;=2.14.1 JNDI features that are used in configuration, log messages, and parameters do not protect against ...]]></description>
				</item>
												<item>
					<title>XStream vulnerable to arbitrary execution of code</title>
					<link>http://dotcms.com/security/SI-57</link>
					<guid>http://dotcms.com/security/SI-57</guid>
					<pubDate>Wed, 19 May 2021 05:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;An issue was discovered in dotCMS 3.0 through 5.3.8.4 and 20.10 through 21.04. When PUTting or POSTing content via &lt;strong&gt;/api/content&lt;/strong&gt; in the XML format, the processed XML stream, at unmarshalling time, contains type information to recreate the...]]></description>
				</item>
												<item>
					<title>Authenticated User SQL Injection Vulnerability in api</title>
					<link>http://dotcms.com/security/SI-56</link>
					<guid>http://dotcms.com/security/SI-56</guid>
					<pubDate>Fri, 30 Oct 2020 05:15:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;&lt;span&gt;dotCMS 5.0 through 5.3.9 allows SQL injection by an authenticated user via the system REST api using the endpoint &lt;strong&gt;/api/v1/containers&lt;/strong&gt;.&amp;nbsp; &lt;/span&gt;&lt;span&gt;The classes that are used to paginate results of some &lt;/span&gt;&lt;span&gt;REST requests...]]></description>
				</item>
												<item>
					<title>Authenticated users may instantiate arbitrary Java objects</title>
					<link>http://dotcms.com/security/SI-55</link>
					<guid>http://dotcms.com/security/SI-55</guid>
					<pubDate>Fri, 5 Jun 2020 06:25:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;An authenticated user, with permissions to create and execute Velocity files, can use the Velocity context to execute arbitrary Java objects within the dotCMS code base.  When combined with the creation of script files on the server file system, this could...]]></description>
				</item>
												<item>
					<title>Incorrect access control can lead to information disclosure and remote execution</title>
					<link>http://dotcms.com/security/SI-54</link>
					<guid>http://dotcms.com/security/SI-54</guid>
					<pubDate>Thu, 9 Jan 2020 10:30:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;&lt;span&gt;dotCMS fails to normalize the URI string when checking if a user should have access to a specific directory.&amp;nbsp; If a dotCMS installation stores its assets under the tomcat&apos;s webapps/ROOT/assets directory, then the files and data stored under this...]]></description>
				</item>
												<item>
					<title>SQL Injection Possible By Publisher Role</title>
					<link>http://dotcms.com/security/SI-53</link>
					<guid>http://dotcms.com/security/SI-53</guid>
					<pubDate>Thu, 6 Jun 2019 03:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;If there are bundles that have not been pushed, it is possible for someone&amp;nbsp;with Publisher permissions to use the view_unpushed_bundles.jsp to inject code into SQL.&amp;nbsp;&amp;nbsp;&lt;/p&gt;]]></description>
				</item>
												<item>
					<title>Reflected XSS Vulnerability in forward_js.jsp</title>
					<link>http://dotcms.com/security/SI-52</link>
					<guid>http://dotcms.com/security/SI-52</guid>
					<pubDate>Thu, 23 May 2019 08:45:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;&lt;span&gt;Reflected (non-persistent) Cross Site Scripting (XSS) vulnerability exists in&amp;nbsp;forward_js.jsp.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Can track status here:&amp;nbsp;&amp;nbsp;&lt;a href=&quot;https://github.com/dotCMS/core/issues/16605&quot;&gt;https://github.com/dotCMS/core/issues/16605&lt;/a&gt;&lt;a...]]></description>
				</item>
												<item>
					<title>User Privilege Escalation Possible In Velocity Code</title>
					<link>http://dotcms.com/security/SI-51</link>
					<guid>http://dotcms.com/security/SI-51</guid>
					<pubDate>Fri, 25 Jan 2019 04:00:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;By publishing custom, problematic vtl code, a user is able to elevate their dotCMS permissions for the duration of their browsing session.&lt;/p&gt;
&lt;p&gt;User must have publish permissions to publish the custom vtl file.&lt;/p&gt;
&lt;p&gt;Can track status of the issue here:&amp;nbsp...]]></description>
				</item>
												<item>
					<title>Permissive CORS Policy</title>
					<link>http://dotcms.com/security/SI-50</link>
					<guid>http://dotcms.com/security/SI-50</guid>
					<pubDate>Thu, 24 Jan 2019 04:15:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;dotCMS currently returns a&amp;nbsp;&amp;ldquo;Access-Control-Allow-Origin&amp;rdquo; header with a value of &quot;*&quot;.&amp;nbsp; This means that the default&amp;nbsp; is to share any public content on this server.&amp;nbsp;&amp;nbsp;While this is a browser enforced security measure, it...]]></description>
				</item>
												<item>
					<title>Reflected XSS Vulnerability in referer_js.jsp</title>
					<link>http://dotcms.com/security/SI-49</link>
					<guid>http://dotcms.com/security/SI-49</guid>
					<pubDate>Thu, 24 Jan 2019 04:00:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;Reflected (non-persistent) Cross Site Scripting (XSS) vulnerability exists in&amp;nbsp;&lt;strong&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt;/html/common/referer_common.jsp&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;span style=&quot;font-weight: 400;&quot;&gt;Can track status here:&amp;nbsp;&amp;nbsp;https://github...]]></description>
				</item>
												<item>
					<title>File Upload Vulnerability</title>
					<link>http://dotcms.com/security/SI-48</link>
					<guid>http://dotcms.com/security/SI-48</guid>
					<pubDate>Thu, 10 Jan 2019 04:15:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;A specific dotCMS REST endpoint can be utilized to&amp;nbsp;create files on the server&apos;s filesystem.&lt;/p&gt;
&lt;p&gt;To exploit this vulnerability, the user must be logged into the backend of dotCMS with administrator permissions.&lt;/p&gt;
&lt;p&gt;Status of this issue can be ...]]></description>
				</item>
												<item>
					<title>Client Side URL Redirection</title>
					<link>http://dotcms.com/security/SI-46</link>
					<guid>http://dotcms.com/security/SI-46</guid>
					<pubDate>Thu, 10 Jan 2019 04:00:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;A URL of attackers choice can be passed as a parameter to a specific dotCMS endpoint.&amp;nbsp; This endpoint responds with a 302 redirect which causes the browser to load the URL passed into dotCMS.&amp;nbsp; This could be used a part of a phishing attack or to...]]></description>
				</item>
												<item>
					<title>File Deletion Vulnerability</title>
					<link>http://dotcms.com/security/SI-47</link>
					<guid>http://dotcms.com/security/SI-47</guid>
					<pubDate>Thu, 10 Jan 2019 04:00:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;A specific dotCMS endpoint can be utilized to delete specified files on the server&apos;s filesystem.&lt;/p&gt;
&lt;p&gt;To exploit this vulnerability, the user must be logged into the backend of dotCMS with administrator permissions and use a carefully crafted URL.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Status...]]></description>
				</item>
												<item>
					<title>XSS vulnerability with image tool</title>
					<link>http://dotcms.com/security/SI-44</link>
					<guid>http://dotcms.com/security/SI-44</guid>
					<pubDate>Wed, 3 Oct 2018 20:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;XSS vulnerability exists on&amp;nbsp;&lt;span&gt;/html/portlet/ext/contentlet/image_tools/index.jsp.&amp;nbsp; Please refer to github issue for details:&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/dotCMS/core/issues/15274&quot;&gt;https://github.com/dotCMS/core/issues/15274&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;]]></description>
				</item>
												<item>
					<title>BeanUtil version 1.9.2 and below allows classloader manipulation</title>
					<link>http://dotcms.com/security/SI-45</link>
					<guid>http://dotcms.com/security/SI-45</guid>
					<pubDate>Sat, 1 Sep 2018 05:30:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;&lt;span&gt;dotCMS 3 and 4 series ship with Apache Commons BeanUtils&amp;nbsp;version 1.6.2 and is used in the struts based back end of the dotCMS system.&amp;nbsp; &amp;nbsp;BeanUtils version 1.9.2 and under, including version 1.6.2, do&amp;nbsp;not suppress the class property...]]></description>
				</item>
												<item>
					<title>Read access to restricted files in Tomcat on Windows</title>
					<link>http://dotcms.com/security/SI-43</link>
					<guid>http://dotcms.com/security/SI-43</guid>
					<pubDate>Sun, 12 Mar 2017 20:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;When running on an OS which does not have a case sensitive filesystem (i.e. Windows), you must not run with the &quot;allowLinking&quot; options turned on: &amp;nbsp;&lt;a href=&quot;https://tomcat.apache.org/tomcat-8.0-doc/config/resources.html&quot;&gt;https://tomcat.apache.org/tomcat...]]></description>
				</item>
												<item>
					<title>Upload of file types unrestricted</title>
					<link>http://dotcms.com/security/SI-42</link>
					<guid>http://dotcms.com/security/SI-42</guid>
					<pubDate>Thu, 9 Mar 2017 02:45:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;Authenticated users can uploaded bundles that contain files of any type.&lt;/p&gt;]]></description>
				</item>
												<item>
					<title>Cross-Site Request Forgery (CSRF)</title>
					<link>http://dotcms.com/security/SI-40</link>
					<guid>http://dotcms.com/security/SI-40</guid>
					<pubDate>Thu, 9 Mar 2017 02:30:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;Administrative backend access is vulnerable to CSRF attack. &amp;nbsp;For example, this means that if a user is already logged into the backend of dotCMS and clicks on malicious content (that targets dotCMS) in another tab or window, this malicious content ...]]></description>
				</item>
												<item>
					<title>Bundle path traversal</title>
					<link>http://dotcms.com/security/SI-41</link>
					<guid>http://dotcms.com/security/SI-41</guid>
					<pubDate>Thu, 9 Mar 2017 02:30:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;With a user that is authenticated to the backend, intentionally customized bundles can be uploaded that will write files to arbitrary locations on the filesystem.&lt;/p&gt;]]></description>
				</item>
												<item>
					<title>Blind SQL injection</title>
					<link>http://dotcms.com/security/SI-39</link>
					<guid>http://dotcms.com/security/SI-39</guid>
					<pubDate>Tue, 17 Jan 2017 06:30:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;SQL injection via Categories Servlet - does not require authentication. &amp;nbsp;The only concrete exploit we have at this time is against mySQL 5.5. &amp;nbsp; Since this string does get passed to the DB for evaluation, it is possible that an exploit of this ...]]></description>
				</item>
												<item>
					<title>Captcha can be programmatically reused by passing session id</title>
					<link>http://dotcms.com/security/SI-38</link>
					<guid>http://dotcms.com/security/SI-38</guid>
					<pubDate>Mon, 31 Oct 2016 20:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;If you use a captcha protected resource like the sendEmailServlet you can pass the same captcha again and again via curl if you use the session id cookie of the original request.&lt;/p&gt;
&lt;p&gt;CVE-2016-8600&lt;/p&gt;]]></description>
				</item>
												<item>
					<title>Insufficient authentication in the CMSMaintenanceAjax class</title>
					<link>http://dotcms.com/security/SI-37</link>
					<guid>http://dotcms.com/security/SI-37</guid>
					<pubDate>Wed, 27 Jul 2016 09:15:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;Under certain conditions, it may be possible to invoke the&amp;nbsp;&lt;span&gt;deleteContentletsFromIdList method of the CMSMaintenance class without proper permissions.&lt;/span&gt;&lt;/p&gt;]]></description>
				</item>
												<item>
					<title>SQL Injection from Workflow Screen III</title>
					<link>http://dotcms.com/security/SI-36</link>
					<guid>http://dotcms.com/security/SI-36</guid>
					<pubDate>Tue, 12 Apr 2016 07:15:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;SQL Injection via workflow screen orderby&amp;nbsp;parameter -&amp;nbsp;requires Authentication.&lt;/p&gt;]]></description>
				</item>
												<item>
					<title>SQL Injection via REST api</title>
					<link>http://dotcms.com/security/SI-35</link>
					<guid>http://dotcms.com/security/SI-35</guid>
					<pubDate>Tue, 12 Apr 2016 05:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;A SQL injection attack is possible via the Content REST api if the api is set to allow for anonymous content saving (which is the shipped default).&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;]]></description>
				</item>
												<item>
					<title>Directory traversal vulnerability by Admin</title>
					<link>http://dotcms.com/security/SI-34</link>
					<guid>http://dotcms.com/security/SI-34</guid>
					<pubDate>Mon, 11 Apr 2016 11:30:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;dotCMS provides a mechanism to &quot;tail&quot; a&amp;nbsp;system log files via an online console. &amp;nbsp;It is possible for an Admin (Authenticated user with Admin permissions in the dotCMS system) to specify a file outside of the specified dotCMS log directory to &quot;tail&quot;...]]></description>
				</item>
												<item>
					<title>XSS in Lucene Search Admin tool</title>
					<link>http://dotcms.com/security/SI-33</link>
					<guid>http://dotcms.com/security/SI-33</guid>
					<pubDate>Mon, 11 Apr 2016 10:30:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;The lucene search admin tool (Admin only) allows a user to construct and execute a query to run against dotCMS content. The admin tool does not sanitize the query and echo&apos;s it back to the user&amp;nbsp;which allows for XSS javascript execution.&lt;/p&gt;]]></description>
				</item>
												<item>
					<title>SQL Injection via DWR - Requires Authenticated User</title>
					<link>http://dotcms.com/security/SI-32</link>
					<guid>http://dotcms.com/security/SI-32</guid>
					<pubDate>Mon, 4 Apr 2016 11:30:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;A SQL injection vulnerability has been identified in dotCMS 3.3 which, if successfully exploited, could allow an attacker to access sensitive information in the dotcms database. &amp;nbsp;&amp;nbsp;&lt;br /&gt;&lt;br /&gt;The vulnerability requires an authenticated dotCMS ...]]></description>
				</item>
												<item>
					<title>CSRF Add User</title>
					<link>http://dotcms.com/security/SI-31</link>
					<guid>http://dotcms.com/security/SI-31</guid>
					<pubDate>Mon, 30 Nov 2015 17:15:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;It is possible to use a well formed POST&amp;nbsp;to the DWR USer endpoint and add a new blank user to the dotCMS system. &amp;nbsp;This user will not be provisioned or permissioned in any way, though will be a valid user in the system.&lt;/p&gt;
&lt;p&gt;Using this method...]]></description>
				</item>
												<item>
					<title>SQL Injection from Workflow Screen II</title>
					<link>http://dotcms.com/security/SI-30</link>
					<guid>http://dotcms.com/security/SI-30</guid>
					<pubDate>Mon, 30 Nov 2015 10:00:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;SQL injection is a method of attack where an attacker can exploit vulnerable code and the type of data an application will accept, and can be exploited in any application parameter that influences a database query. Examples include parameters within the...]]></description>
				</item>
												<item>
					<title>SSRF Vulnerability in RESTful ContentAPI</title>
					<link>http://dotcms.com/security/SI-29</link>
					<guid>http://dotcms.com/security/SI-29</guid>
					<pubDate>Mon, 30 Nov 2015 10:00:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;It is possible to force a remote dotCMS server to make an external request for a remote URL.&lt;/p&gt;
&lt;p&gt;This does not&amp;nbsp;constitute &quot;critical&quot; security flaws in dotCMS because the nature of a critical SSRF vulnerability is to either expose data from an internal...]]></description>
				</item>
												<item>
					<title>jsps exposed to non-authenticated users</title>
					<link>http://dotcms.com/security/SI-28</link>
					<guid>http://dotcms.com/security/SI-28</guid>
					<pubDate>Tue, 23 Sep 2014 20:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;There are some administrative jsps that are accessible to non-administrative users. &amp;nbsp;This allows an attacker to target and call those jsps directly from their browsers without authentication.&lt;/p&gt;]]></description>
				</item>
												<item>
					<title>XSS on &quot;page not found .jsp&quot;</title>
					<link>http://dotcms.com/security/SI-27</link>
					<guid>http://dotcms.com/security/SI-27</guid>
					<pubDate>Tue, 23 Sep 2014 08:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;&amp;nbsp;GET Parameter &quot;url&quot; is displayed back to output without proper escaping. &amp;nbsp;&lt;/p&gt;]]></description>
				</item>
												<item>
					<title>CRLF Header Injection vulnerability</title>
					<link>http://dotcms.com/security/SI-26</link>
					<guid>http://dotcms.com/security/SI-26</guid>
					<pubDate>Thu, 17 Jul 2014 11:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;Scanning software (Acunetix) has reported a&amp;nbsp;CRLF Injection&amp;nbsp;vulnerability in the&amp;nbsp;htmlpdf servlet.&lt;/p&gt;
&lt;p&gt;I have discussed this report with our Dotcms developers and they feel the report is correct and the problem is located in the Dotcms codebase...]]></description>
				</item>
												<item>
					<title>Password fields with enabled autocomplete</title>
					<link>http://dotcms.com/security/SI-25</link>
					<guid>http://dotcms.com/security/SI-25</guid>
					<pubDate>Mon, 21 Apr 2014 11:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;The enabled password &amp;ldquo;autocomplete&amp;rdquo; feature allows the storage of the dotCMS credentials on the client. A attacker with physical access to the client is able to retrieve the credentials by extracting it from the browsers password storage.&lt;/p&gt;]]></description>
				</item>
												<item>
					<title>Missing Cookie Security Attribute &#8220;httpOnly&#8221;</title>
					<link>http://dotcms.com/security/SI-24</link>
					<guid>http://dotcms.com/security/SI-24</guid>
					<pubDate>Mon, 21 Apr 2014 11:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;The used session cookie can be read by client side code using JavaScript. This means that a Cross Site Scripting vulnerability in the page allows a attacker to retrieve the session cookie and therefore log in to the administrative interface without a password...]]></description>
				</item>
												<item>
					<title>HTTP header injection</title>
					<link>http://dotcms.com/security/SI-23</link>
					<guid>http://dotcms.com/security/SI-23</guid>
					<pubDate>Mon, 21 Apr 2014 07:30:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;A header injection allows a attacker to insert arbitrary HTTP-Headers into the server&amp;rsquo;s response. This enables a attacker to change cookie values, add additional headers or in the case of a normal page to insert arbitrary code that gets executed as...]]></description>
				</item>
												<item>
					<title>Arbitrary URL redirects</title>
					<link>http://dotcms.com/security/SI-22</link>
					<guid>http://dotcms.com/security/SI-22</guid>
					<pubDate>Mon, 21 Apr 2014 07:15:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;Using an arbitrary URL redirect a attacker is able to send visiting clients to a web site of the attacker&amp;rsquo;s choosing. To successfully mount such a attack the attacker prepares a link to the dotCMS site that looks like a innocent link to an article...]]></description>
				</item>
												<item>
					<title>Information disclosure through unauthenticated and unused scripts</title>
					<link>http://dotcms.com/security/SI-21</link>
					<guid>http://dotcms.com/security/SI-21</guid>
					<pubDate>Mon, 21 Apr 2014 07:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;A attacker can use the discovered scripts to obtain a information about the server and it&amp;rsquo;s configuration. Including the internal IP address, hostname and other dotCMS configuration parameters. This can be leveraged in later attacks to further attack...]]></description>
				</item>
												<item>
					<title>Vulnerabilities in &#8220;Comments&#8221; feature</title>
					<link>http://dotcms.com/security/SI-20</link>
					<guid>http://dotcms.com/security/SI-20</guid>
					<pubDate>Mon, 21 Apr 2014 06:45:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;dotCMS employs a &amp;ldquo;Comments&amp;rdquo; feature that allows logged in users to comment on articles and pages. Proper security checks are missing so this feature can be misused by a attacker to post comments to the pages or use the &amp;ldquo;approve comment&amp;rdquo...]]></description>
				</item>
												<item>
					<title>Cross Site Scripting filter bypass</title>
					<link>http://dotcms.com/security/SI-19</link>
					<guid>http://dotcms.com/security/SI-19</guid>
					<pubDate>Mon, 21 Apr 2014 06:15:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;The Cross Site Scripting protection, that is responsible for filtering user input to provide a sanitized representation of potentially harmful input, is flawed and can easily be circumvented. This leads to a range of vulnerabilities that allow attackers...]]></description>
				</item>
												<item>
					<title>Arbitrary Command Execution</title>
					<link>http://dotcms.com/security/SI-18</link>
					<guid>http://dotcms.com/security/SI-18</guid>
					<pubDate>Mon, 21 Apr 2014 06:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;This vulnerability allow authenticated users to view arbitrary files on the server and execute commands on the systems as the user that is running dotCMS on the server. This potentially leads to a full compromise of the server if a high privileged user ...]]></description>
				</item>
												<item>
					<title>Forgot Password generates weak password</title>
					<link>http://dotcms.com/security/SI-17</link>
					<guid>http://dotcms.com/security/SI-17</guid>
					<pubDate>Mon, 21 Apr 2014 04:45:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;The vulnerabilities in the user account management allow attackers to circumvent the access controls by brute-forcing weak passwords and using default users to gain possible access to administrative interface. The implementation of the password reset function...]]></description>
				</item>
												<item>
					<title>Stored XSS possible in admin tool as authenticated user</title>
					<link>http://dotcms.com/security/SI-16</link>
					<guid>http://dotcms.com/security/SI-16</guid>
					<pubDate>Wed, 3 Jul 2013 03:45:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;In a number of areas in the dotCMS Administrative tool, it is possible for an authenticated user to create stored XSS that executes in the admin user&apos;s browser.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;In the browser once logged into the admin screen you can use XSS. ...]]></description>
				</item>
												<item>
					<title>AJAX requests without a session ID or other form of authentication</title>
					<link>http://dotcms.com/security/SI-15</link>
					<guid>http://dotcms.com/security/SI-15</guid>
					<pubDate>Tue, 18 Jun 2013 10:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;It is possible to create a user account (without privileges) using a properly formated remote AJAX call.&lt;/p&gt;]]></description>
				</item>
												<item>
					<title>XSS Vulnerability on Login Page</title>
					<link>http://dotcms.com/security/SI-14</link>
					<guid>http://dotcms.com/security/SI-14</guid>
					<pubDate>Tue, 18 Jun 2013 06:30:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;Input passed via multiple POST parameters to multiple scripts is not&lt;br /&gt;properly sanitised before being returned to the user. This can be exploited&lt;br /&gt;to execute arbitrary HTML and script code in a user&apos;s browser session in&lt;br /&gt;context of an affected...]]></description>
				</item>
												<item>
					<title>Cross Site Request Forgery (XSRF or CSRF)</title>
					<link>http://dotcms.com/security/SI-13</link>
					<guid>http://dotcms.com/security/SI-13</guid>
					<pubDate>Mon, 10 Jun 2013 07:30:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;Cross-Site Request Forgery (XSRF or CSRF) has been detected when using the dotCMS admin tools once a user has been authenticated. Because browsers can run code sent by multiple sites, an XSRF attack can occur if one site sends a request (never seen by the...]]></description>
				</item>
												<item>
					<title>Possible Clickjacking / no frame busting code in dotCMS admin</title>
					<link>http://dotcms.com/security/SI-12</link>
					<guid>http://dotcms.com/security/SI-12</guid>
					<pubDate>Sat, 8 Jun 2013 08:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;It is possible to &quot;clickjack&quot; the dotCMS admin console, which works in a frameset. We need to add the &quot;X-Frame-Options: Deny&quot; / &quot;X-Frame-Options: Sameorigin&quot; header to all requests (both CMS admin and end-user requests).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;- For older browsers...]]></description>
				</item>
												<item>
					<title>Test pages shipped in product</title>
					<link>http://dotcms.com/security/SI-11</link>
					<guid>http://dotcms.com/security/SI-11</guid>
					<pubDate>Fri, 7 Jun 2013 12:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;Testing-related application pages were found within dotCMS. Test pages are usually implemented ad-hoc and often do not adhere to the security requirements/guidelines of the rest of the application, making them a potential security hazard. Recommendations...]]></description>
				</item>
												<item>
					<title>Insecure Browser Caching</title>
					<link>http://dotcms.com/security/SI-10</link>
					<guid>http://dotcms.com/security/SI-10</guid>
					<pubDate>Fri, 7 Jun 2013 11:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;It has been reported that many dotCMS Admin screens do not include Cache-Control headers. &amp;nbsp;This can allow a client browser to cache dotCMS admin pages (as rendered) locally on the client&apos;s computer, which if examined, could expose sensitive content...]]></description>
				</item>
												<item>
					<title>Use of Persistent Cookies</title>
					<link>http://dotcms.com/security/SI-9</link>
					<guid>http://dotcms.com/security/SI-9</guid>
					<pubDate>Wed, 5 Jun 2013 08:15:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;Cookies are small bits of data that are sent by the web application but stored locally in the browser. dotCMS uses a cookie to pass information stored in cookies such as session Identifiers, personalization and customization information, and in rare cases...]]></description>
				</item>
												<item>
					<title>SQL Injection from Workflow Screen</title>
					<link>http://dotcms.com/security/SI-8</link>
					<guid>http://dotcms.com/security/SI-8</guid>
					<pubDate>Wed, 5 Jun 2013 06:45:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;SQL injection is a method of attack where an attacker can exploit vulnerable code and the type of data an application will accept, and can be exploited in any application parameter that influences a database query. Examples include parameters within the...]]></description>
				</item>
												<item>
					<title>Possible Cross Site Redirect</title>
					<link>http://dotcms.com/security/SI-7</link>
					<guid>http://dotcms.com/security/SI-7</guid>
					<pubDate>Tue, 4 Jun 2013 09:45:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;dotCMS needs to ensure application cannot redirect to external sites and Redirects using the referer parameter need to be checked against a lookup table of known-pages for redirection.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It is possible to utilise the application to redirect a...]]></description>
				</item>
												<item>
					<title>Cross Domain Scripts Included Within Application</title>
					<link>http://dotcms.com/security/SI-6</link>
					<guid>http://dotcms.com/security/SI-6</guid>
					<pubDate>Tue, 4 Jun 2013 07:45:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;The web application was found to include JavaScript hosted on third party servers within the application:&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;https://ajax.googleapis.com/ajax/libs/chrome-frame/1/CFInstall.min.js&quot;&gt;https://ajax.googleapis.com/ajax/libs/chrome-frame/1/CFInstall...]]></description>
				</item>
												<item>
					<title>XSS possible after admin authentication</title>
					<link>http://dotcms.com/security/SI-5</link>
					<guid>http://dotcms.com/security/SI-5</guid>
					<pubDate>Sun, 2 Jun 2013 08:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;A number of user input fields within the administrative portal of the application were discovered to accept arbitrary user input that could be returned to the page. One example location where a script could be injected is the page title field of a new HTML...]]></description>
				</item>
												<item>
					<title>XSS error on the account login page</title>
					<link>http://dotcms.com/security/SI-4</link>
					<guid>http://dotcms.com/security/SI-4</guid>
					<pubDate>Sun, 9 Sep 2012 20:00:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;1.&lt;/p&gt;
&lt;p&gt;XSS in&amp;nbsp;&lt;a href=&quot;http://dotcms.constantcontact.com/c/portal_public/login&quot;&gt;http://dotcms.constantcontact.com/c/portal_public/login&lt;/a&gt;&amp;nbsp;&lt;br /&gt;on the my_account_logon paramter (the User ID field on the login form)&lt;/p&gt;
&lt;p&gt;my_account_logon=&apos;&quot;&apos;&amp;gt...]]></description>
				</item>
												<item>
					<title>dotCMS template permissions allow arbitrary code execution</title>
					<link>http://dotcms.com/security/SI-3</link>
					<guid>http://dotcms.com/security/SI-3</guid>
					<pubDate>Thu, 12 Apr 2012 20:00:00 -0400</pubDate>
					<description><![CDATA[&lt;h3&gt;Overview&lt;/h3&gt;
&lt;p&gt;The dotCMS content management system version 1.9 and possibly earlier versions, contains a vulnerability that allows users with admin access the appropriate permissions to create a malicious template with arbitrary code.&amp;nbsp;An authenticated...]]></description>
				</item>
												<item>
					<title>Cookies do not require SSL</title>
					<link>http://dotcms.com/security/SI-2</link>
					<guid>http://dotcms.com/security/SI-2</guid>
					<pubDate>Mon, 6 Jun 2011 07:45:00 -0400</pubDate>
					<description><![CDATA[&lt;p&gt;Many security policies state that any area of the website or web application that contains sensitive information or access to privileged functionality such as remote site administration requires that all cookies are sent via SSL during an SSL session. The...]]></description>
				</item>
												<item>
					<title>Problem with XSS attack on 404 page</title>
					<link>http://dotcms.com/security/SI-1</link>
					<guid>http://dotcms.com/security/SI-1</guid>
					<pubDate>Sun, 6 Feb 2011 19:00:00 -0500</pubDate>
					<description><![CDATA[&lt;p&gt;dotCMS has code in the CMSFilter that try to solve issues with XSS attacks, but that code is never called by the 404 page.&lt;br /&gt;&lt;br /&gt;This is becuase for all velocity served by the CMS, we use something called&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;- com.dotmarketing...]]></description>
				</item>
						</channel>
</rss>