From 286e89ea366b045ae7a208a2fcde658ad39ed756 Mon Sep 17 00:00:00 2001 From: cktricky Date: Tue, 19 Aug 2014 12:32:19 -0400 Subject: [PATCH] removed the tutorial snippet about using Rails 3.2.11 since this is no longer the case; under the insecure components section. Also, changed the partials name to first (from second), and renumbered the collapsable sections. Ran tests, all seems good to go --- .../_insecure_components_first.html.erb | 62 +++++++--- .../_insecure_components_second.html.erb | 109 ------------------ .../tutorials/insecure_components.html.erb | 5 - 3 files changed, 45 insertions(+), 131 deletions(-) delete mode 100644 app/views/layouts/tutorial/insecure_components/_insecure_components_second.html.erb diff --git a/app/views/layouts/tutorial/insecure_components/_insecure_components_first.html.erb b/app/views/layouts/tutorial/insecure_components/_insecure_components_first.html.erb index 16c8060..3f90c41 100644 --- a/app/views/layouts/tutorial/insecure_components/_insecure_components_first.html.erb +++ b/app/views/layouts/tutorial/insecure_components/_insecure_components_first.html.erb @@ -1,7 +1,7 @@
- A9 - Using Components with Known Vulnerabilities (Rack / Rails) + A9 - Using Components with Known Vulnerabilities (DOM XSS / JQuery Snippet)
@@ -16,9 +16,7 @@
-

- Virtually every application has these issues because most development teams don’t focus on ensuring their components/libraries are up to date. In many cases, the developers don’t even know all the components they are using, never mind their versions. Component dependencies make things even worse. -

+ JQuery Snippet contains at least one DOM-Based XSS vulnerability that can be confirmed in IE11. Unknowingly, the Railsgoat development team used this library. Credit for vulnerability discovery as well as submission to <%= link_to "@raesene", "http://github.com/raesene", {:style => "color: rgb(181, 121, 158)", :target => "_blank"}%>. This was unintentional but goes to show how easily vulnerabilities can creep in when using third-party libraries.
@@ -32,17 +30,33 @@
-

- Within the Gemfile the following gem versions are set. These versions of Rails and Rack are both vulnerable to multiple attacks. -

- 
-        <%= %q{
-          gem 'rails', '3.2.11'
-          gem 'rack', '1.4.3'
-        } %>
-

+ Within the file app/assets/javascripts/jquery.snippet.js:

+ 
+        <%= %{
+// snippet new window popup function
+function snippetPopup(content) \{
+   top.consoleRef=window.open('','myconsole',
+    'width=600,height=300'
+     +',left=50,top=50'
+     +',menubar=0'
+     +',toolbar=0'
+     +',location=0'
+     +',status=0'
+     +',scrollbars=1'
+     +',resizable=1');
+   top.consoleRef.document.writeln(
+    'Snippet :: Code View :: '+}%><span style="background-color:yellow">location.href</span><%= %{+''
+     +''
+     +'
'+content+'
'
+     +''
+   );
+   top.consoleRef.document.close();
+\}}%>
+

+ We can see that the location.href DOM property is used to dynamically generate a title for the text box pop-up. This value is string concatenated directly from the DOM without first performing some escaping routine or HTML encoding. +

@@ -56,9 +70,23 @@
-

- To fix this issue, simply update your gems after unpinning the gem versions. You should always run the most up to date version possible and run Bundler-Audit Regularly. -

+

Using Components with Known Vulnerabilities (DOM XSS) - ATTACK

+

+ In order to demonstrate that you can indeed perform DOM XSS through this coding error, we will use a simple alert box. This does not appear to work in Chrome, Safari, or Firefox as they first URL encoded the script portion of the url before rendering which complicates browser interpretation. IE on the other hand, true to form, is totally vulnerable. The following example assumes you are running Railsgoat on localhost, port 3000. If this is the case, open IE, paste the URL (below) into IE. +

+ 
+<%= "http://localhost:3000/tutorials/injection#" %>
+
+

+ The portion after the pound (#) symbol will close off the title and head portions of the HTML and then allow for properly generated JavaScript to be rendered and executed. After browsing to this URL, navigate to the tutorial where code snippets are shown and click on the "pop-up" link that appears after hovering over the code snippet. This should be all that is required to demonstrate DOM-XSS. +

+

Using Components with Known Vulnerabilities (DOM XSS) - SOLUTION

+

+ Use the hoganEscape() function defined in application.js to solve this problem. For instance: +

+ 
+<%=%{'Snippet :: Code View :: '+}%><span style="background-color:yellow">hoganEscape(location.href)</span> <%=%{+'' }%>
+
@@ -72,7 +100,7 @@
- Remeber to keep your gems up to date! + Review the JQuery Code Snippet for any content that might be mirrored or reflected back and that is under our control.
diff --git a/app/views/layouts/tutorial/insecure_components/_insecure_components_second.html.erb b/app/views/layouts/tutorial/insecure_components/_insecure_components_second.html.erb deleted file mode 100644 index 45d212e..0000000 --- a/app/views/layouts/tutorial/insecure_components/_insecure_components_second.html.erb +++ /dev/null @@ -1,109 +0,0 @@ -
-
-
- A9 - Using Components with Known Vulnerabilities (DOM XSS / JQuery Snippet) -
-
-
-
-
-
- - - - Description - -
-
-
- JQuery Snippet contains at least one DOM-Based XSS vulnerability that can be confirmed in IE11. Unknowingly, the Railsgoat development team used this library. Credit for vulnerability discovery as well as submission to <%= link_to "@raesene", "http://github.com/raesene", {:style => "color: rgb(181, 121, 158)", :target => "_blank"}%>. This was unintentional but goes to show how easily vulnerabilities can creep in when using third-party libraries. -
-
-
-
-
- - - - Bug - -
-
-
-

- Within the file app/assets/javascripts/jquery.snippet.js: -

- 
-        <%= %{
-// snippet new window popup function
-function snippetPopup(content) \{
-   top.consoleRef=window.open('','myconsole',
-    'width=600,height=300'
-     +',left=50,top=50'
-     +',menubar=0'
-     +',toolbar=0'
-     +',location=0'
-     +',status=0'
-     +',scrollbars=1'
-     +',resizable=1');
-   top.consoleRef.document.writeln(
-    'Snippet :: Code View :: '+}%><span style="background-color:yellow">location.href</span><%= %{+''
-     +''
-     +'
'+content+'
'
-     +''
-   );
-   top.consoleRef.document.close();
-\}}%>
-

- We can see that the location.href DOM property is used to dynamically generate a title for the text box pop-up. This value is string concatenated directly from the DOM without first performing some escaping routine or HTML encoding. -

-
-
-
-
-
- - - - Solution - -
-
-
-

Using Components with Known Vulnerabilities (DOM XSS) - ATTACK

-

- In order to demonstrate that you can indeed perform DOM XSS through this coding error, we will use a simple alert box. This does not appear to work in Chrome, Safari, or Firefox as they first URL encoded the script portion of the url before rendering which complicates browser interpretation. IE on the other hand, true to form, is totally vulnerable. The following example assumes you are running Railsgoat on localhost, port 3000. If this is the case, open IE, paste the URL (below) into IE. -

- 
-<%= "http://localhost:3000/tutorials/injection#" %>
-
-

- The portion after the pound (#) symbol will close off the title and head portions of the HTML and then allow for properly generated JavaScript to be rendered and executed. After browsing to this URL, navigate to the tutorial where code snippets are shown and click on the "pop-up" link that appears after hovering over the code snippet. This should be all that is required to demonstrate DOM-XSS. -

-

Using Components with Known Vulnerabilities (DOM XSS) - SOLUTION

-

- Use the hoganEscape() function defined in application.js to solve this problem. For instance: -

- 
-<%=%{'Snippet :: Code View :: '+}%><span style="background-color:yellow">hoganEscape(location.href)</span> <%=%{+'' }%>
-
-
-
-
-
-
- - - - Hint - -
-
-
- Review the JQuery Code Snippet for any content that might be mirrored or reflected back and that is under our control. -
-
-
-
-
-
\ No newline at end of file diff --git a/app/views/tutorials/insecure_components.html.erb b/app/views/tutorials/insecure_components.html.erb index 8d11c80..e9fb34e 100644 --- a/app/views/tutorials/insecure_components.html.erb +++ b/app/views/tutorials/insecure_components.html.erb @@ -5,11 +5,6 @@ <%= render :partial => "layouts/tutorial/insecure_components/insecure_components_first" %> -
-
- <%= render :partial => "layouts/tutorial/insecure_components/insecure_components_second" %> -
-