ID CVE-2013-1857
Summary The sanitize helper in lib/action_controller/vendor/html-scanner/html/sanitizer.rb in the Action Pack component in Ruby on Rails before 2.3.18, 3.0.x and 3.1.x before 3.1.12, and 3.2.x before 3.2.13 does not properly handle encoded : (colon) characters in URLs, which makes it easier for remote attackers to conduct cross-site scripting (XSS) attacks via a crafted scheme name, as demonstrated by including a : sequence.
References
Vulnerable Configurations
  • Red Hat Enterprise Linux 6.0
    cpe:2.3:o:redhat:enterprise_linux:6.0
  • Ruby on Rails 0.5.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.5.0
  • Ruby on Rails 0.5.5
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.5.5
  • Ruby on Rails 0.5.6
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.5.6
  • Ruby on Rails 0.5.7
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.5.7
  • Ruby on Rails 0.6.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.6.0
  • Ruby on Rails 0.6.5
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.6.5
  • Ruby on Rails 0.7.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.7.0
  • Ruby on Rails 0.8.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.8.0
  • Ruby on Rails 0.8.5
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.8.5
  • Ruby on Rails 0.9.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.9.0
  • Ruby on Rails 0.9.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.9.1
  • Ruby on Rails 0.9.2
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.9.2
  • Ruby on Rails 0.9.3
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.9.3
  • Ruby on Rails 0.9.4
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.9.4
  • Ruby on Rails 0.9.4.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.9.4.1
  • Ruby on Rails 0.10.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.10.0
  • Ruby on Rails 0.10.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.10.1
  • Ruby on Rails 0.11.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.11.0
  • Ruby on Rails 0.11.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.11.1
  • Ruby on Rails 0.12.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.12.0
  • Ruby on Rails 0.12.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.12.1
  • Ruby on Rails 0.13.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.13.0
  • Ruby on Rails 0.13.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.13.1
  • Ruby on Rails 0.14.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.14.1
  • Ruby on Rails 0.14.2
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.14.2
  • Ruby on Rails 0.14.3
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.14.3
  • Ruby on Rails 0.14.4
    cpe:2.3:a:rubyonrails:ruby_on_rails:0.14.4
  • Ruby on Rails 1.0.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.0.0
  • Ruby on Rails 1.1.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.1.0
  • Ruby on Rails 1.1.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.1.1
  • Ruby on Rails 1.1.2
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.1.2
  • Ruby on Rails 1.1.3
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.1.3
  • Ruby on Rails 1.1.4
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.1.4
  • Ruby on Rails 1.1.5
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.1.5
  • Ruby on Rails 1.1.6
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.1.6
  • Ruby on Rails 1.2.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.2.0
  • Ruby on Rails 1.2.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.2.1
  • Ruby on Rails 1.2.2
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.2.2
  • Ruby on Rails 1.2.3
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.2.3
  • Ruby on Rails 1.2.4
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.2.4
  • Ruby on Rails 1.2.5
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.2.5
  • Ruby on Rails 1.2.6
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.2.6
  • Ruby on Rails 1.9.5
    cpe:2.3:a:rubyonrails:ruby_on_rails:1.9.5
  • Ruby on Rails 2.0.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.0.0
  • Ruby on Rails 2.0.0 release Candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.0.0:rc1
  • Ruby on Rails 2.0.0 release Candidate 2
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.0.0:rc2
  • Ruby on Rails 2.0.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.0.1
  • Ruby on Rails 2.0.2
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.0.2
  • Ruby on Rails 2.0.4
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.0.4
  • Ruby on Rails 2.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.1
  • Ruby on Rails 2.1.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.1.0
  • Ruby on Rails 2.1.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.1.1
  • Ruby on Rails 2.1.2
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.1.2
  • Ruby on Rails 2.2.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.2.0
  • Ruby on Rails 2.2.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.2.1
  • Ruby on Rails 2.2.2
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.2.2
  • Ruby on Rails 2.3.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.0
  • Ruby on Rails 2.3.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.1
  • Ruby on Rails 2.3.2
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.2
  • Ruby on Rails 2.3.3
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.3
  • Ruby on Rails 2.3.4
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.4
  • Ruby on Rails 2.3.9
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.9
  • Ruby on Rails 2.3.10
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.10
  • Ruby on Rails 2.3.11
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.11
  • Ruby on Rails 2.3.12
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.12
  • Ruby on Rails 2.3.13
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.13
  • Ruby on Rails 2.3.14
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.14
  • Ruby on Rails 2.3.15
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.15
  • Ruby on Rails 2.3.16
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.16
  • cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.17
    cpe:2.3:a:rubyonrails:ruby_on_rails:2.3.17
  • Ruby on Rails 3.0.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.0
  • Ruby on Rails 3.0.0 beta
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.0:beta
  • Ruby on Rails 3.0.0 beta2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.0:beta2
  • Ruby on Rails 3.0.0 beta3
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.0:beta3
  • Ruby on Rails 3.0.0 beta4
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.0:beta4
  • Ruby on Rails 3.0.0 release candidate
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.0:rc
  • Ruby on Rails 3.0.0 release candidate 2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.0:rc2
  • Ruby on Rails 3.0.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.1
  • Ruby on Rails 3.0.1 pre
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.1:pre
  • Ruby on Rails 3.0.2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.2
  • Ruby on Rails 3.0.2 pre
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.2:pre
  • Ruby on Rails 3.0.3
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.3
  • Ruby on Rails 3.0.4
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.4
  • Ruby on Rails 3.0.4 release candidate
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.4:rc
  • Ruby on Rails 3.0.4 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.4:rc1
  • Ruby on Rails 3.0.5
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.5
  • Ruby on Rails 3.0.5 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.5:rc1
  • Ruby on Rails 3.0.6
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.6
  • Ruby on Rails 3.0.6 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.6:rc1
  • Ruby on Rails 3.0.6 release candidate 2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.6:rc2
  • Ruby on Rails 3.0.7
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.7
  • Ruby on Rails 3.0.7 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.7:rc1
  • Ruby on Rails 3.0.7 release candidate 2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.7:rc2
  • Ruby on Rails 3.0.8
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.8
  • Ruby on Rails 3.0.8 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.8:rc1
  • Ruby on Rails 3.0.8 release candidate 2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.8:rc2
  • Ruby on Rails 3.0.8 release candidate 3
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.8:rc3
  • Ruby on Rails 3.0.8 release candidate 4
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.8:rc4
  • Ruby on Rails 3.0.9
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.9
  • Ruby on Rails 3.0.9 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.9:rc1
  • Ruby on Rails 3.0.9 release candidate 2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.9:rc2
  • Ruby on Rails 3.0.9 release candidate 3
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.9:rc3
  • Ruby on Rails 3.0.9 release candidate 4
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.9:rc4
  • Ruby on Rails 3.0.9 release candidate 5
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.9:rc5
  • Ruby on Rails 3.0.10
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.10
  • Ruby on Rails 3.0.10 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.10:rc1
  • Ruby on Rails 3.0.11
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.11
  • Ruby on Rails 3.0.12
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.12
  • Ruby on Rails 3.0.12 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.12:rc1
  • Ruby on Rails 3.0.13
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.13
  • Ruby on Rails 3.0.13 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.13:rc1
  • Ruby on Rails 3.0.14
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.14
  • Ruby on Rails 3.0.16
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.16
  • Ruby on Rails 3.0.17
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.17
  • Ruby on Rails 3.0.18
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.18
  • Ruby on Rails 3.0.19
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.19
  • Ruby on Rails 3.0.20
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.0.20
  • Ruby on Rails 3.1.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.0
  • Ruby on Rails 3.1.0 beta 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.0:beta1
  • Ruby on Rails 3.1.0 release Candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.0:rc1
  • Ruby on Rails 3.1.0 release Candidate 2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.0:rc2
  • Ruby on Rails 3.1.0 release Candidate 3
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.0:rc3
  • Ruby on Rails 3.1.0 release Candidate 4
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.0:rc4
  • Ruby on Rails 3.1.0 release Candidate 5
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.0:rc5
  • Ruby on Rails 3.1.0 release Candidate 6
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.0:rc6
  • Ruby on Rails 3.1.0 release Candidate 7
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.0:rc7
  • Ruby on Rails 3.1.0 release Candidate 8
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.0:rc8
  • Ruby on Rails 3.1.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.1
  • Ruby on Rails 3.1.1 release Candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.1:rc1
  • Ruby on Rails 3.1.1 release Candidate 2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.1:rc2
  • Ruby on Rails 3.1.1 release Candidate 3
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.1:rc3
  • Ruby on Rails 3.1.2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.2
  • Ruby on Rails 3.1.2 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.2:rc1
  • Ruby on Rails 3.1.2 release candidate 2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.2:rc2
  • Ruby on Rails 3.1.3
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.3
  • Ruby on Rails 3.1.4
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.4
  • Ruby on Rails 3.1.4 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.4:rc1
  • Ruby on Rails 3.1.5
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.5
  • Ruby on Rails 3.1.5 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.5:rc1
  • Ruby on Rails 3.1.6
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.6
  • Ruby on Rails 3.1.7
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.7
  • Ruby on Rails 3.1.8
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.8
  • Ruby on Rails 3.1.9
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.9
  • Ruby on Rails 3.1.10
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.10
  • cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.11
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.1.11
  • Ruby on Rails 3.2.0
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.0
  • Ruby on Rails 3.2.0 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.0:rc1
  • Ruby on Rails 3.2.0 release candidate 2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.0:rc2
  • Ruby on Rails 3.2.1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.1
  • Ruby on Rails 3.2.2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.2
  • Ruby on Rails 3.2.2 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.2:rc1
  • Ruby on Rails 3.2.3
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.3
  • Ruby on Rails 3.2.3 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.3:rc1
  • Ruby on Rails 3.2.3 release candidate2
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.3:rc2
  • Ruby on Rails 3.2.4
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.4
  • Ruby on Rails 3.2.4 release candidate 1
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.4:rc1
  • Ruby on Rails 3.2.5
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.5
  • Ruby on Rails 3.2.6
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.6
  • Ruby on Rails 3.2.7
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.7
  • Ruby on Rails 3.2.8
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.8
  • Ruby on Rails 3.2.9
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.9
  • Ruby on Rails 3.2.10
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.10
  • Ruby on Rails 3.2.11
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.11
  • Ruby on Rails 3.2.12
    cpe:2.3:a:rubyonrails:ruby_on_rails:3.2.12
CVSS
Base: 4.3 (as of 25-09-2015 - 12:41)
Impact:
Exploitability:
CWE CWE-79
CAPEC
  • Cross Site Scripting through Log Files
    An attacker may leverage a system weakness where logs are susceptible to log injection to insert scripts into the system's logs. If these logs are later viewed by an administrator through a thin administrative interface and the log data is not properly HTML encoded before being written to the page, the attackers' scripts stored in the log will be executed in the administrative interface with potentially serious consequences. This attack pattern is really a combination of two other attack patterns: log injection and stored cross site scripting.
  • Embedding Scripts in Non-Script Elements
    This attack is a form of Cross-Site Scripting (XSS) where malicious scripts are embedded in elements that are not expected to host scripts such as image tags (<img>), comments in XML documents (< !-CDATA->), etc. These tags may not be subject to the same input validation, output validation, and other content filtering and checking routines, so this can create an opportunity for an attacker to tunnel through the application's elements and launch a XSS attack through other elements. As with all remote attacks, it is important to differentiate the ability to launch an attack (such as probing an internal network for unpatched servers) and the ability of the remote attacker to collect and interpret the output of said attack.
  • Embedding Scripts within Scripts
    An attack of this type exploits a programs' vulnerabilities that are brought on by allowing remote hosts to execute scripts. The attacker leverages this capability to execute scripts to execute his/her own script by embedding it within other scripts that the target software is likely to execute. The attacker must have the ability to inject script into script that is likely to be executed. If this is done, then the attacker can potentially launch a variety of probes and attacks against the web server's local environment, in many cases the so-called DMZ, back end resources the web server can communicate with, and other hosts. With the proliferation of intermediaries, such as Web App Firewalls, network devices, and even printers having JVMs and Web servers, there are many locales where an attacker can inject malicious scripts. Since this attack pattern defines scripts within scripts, there are likely privileges to execute said attack on the host. Of course, these attacks are not solely limited to the server side, client side scripts like Ajax and client side JavaScript can contain malicious scripts as well. In general all that is required is for there to be sufficient privileges to execute a script, but not protected against writing.
  • Cross-Site Scripting in Error Pages
    An attacker distributes a link (or possibly some other query structure) with a request to a third party web server that is malformed and also contains a block of exploit code in order to have the exploit become live code in the resulting error page. When the third party web server receives the crafted request and notes the error it then creates an error message that echoes the malformed message, including the exploit. Doing this converts the exploit portion of the message into to valid language elements that are executed by the viewing browser. When a victim executes the query provided by the attacker the infected error message error message is returned including the exploit code which then runs in the victim's browser. XSS can result in execution of code as well as data leakage (e.g. session cookies can be sent to the attacker). This type of attack is especially dangerous since the exploit appears to come from the third party web server, who the victim may trust and hence be more vulnerable to deception.
  • Cross-Site Scripting Using Alternate Syntax
    The attacker uses alternate forms of keywords or commands that result in the same action as the primary form but which may not be caught by filters. For example, many keywords are processed in a case insensitive manner. If the site's web filtering algorithm does not convert all tags into a consistent case before the comparison with forbidden keywords it is possible to bypass filters (e.g., incomplete black lists) by using an alternate case structure. For example, the "script" tag using the alternate forms of "Script" or "ScRiPt" may bypass filters where "script" is the only form tested. Other variants using different syntax representations are also possible as well as using pollution meta-characters or entities that are eventually ignored by the rendering engine. The attack can result in the execution of otherwise prohibited functionality.
  • Cross-Site Scripting Using MIME Type Mismatch
    An attacker creates a file with scripting content but where the specified MIME type of the file is such that scripting is not expected. Some browsers will detect that the specified MIME type of the file does not match the actual type of the content and will automatically switch to using an interpreter for the real content type. If the browser does not invoke script filters before doing this, the attackers' script may run on the target unsanitized. For example, the MIME type text/plain may be used where the actual content is text/javascript or text/html. Since text does not contain scripting instructions, the stated MIME type would indicate that filtering is unnecessary. However, if the target application subsequently determines the file's real type and invokes the appropriate interpreter, scripted content could be invoked. In another example, img tags in HTML content could reference a renderable type file instead of an expected image file. The file extension and MIME type can describe an image file, but the file content can be text/javascript or text/html resulting in script execution. If the browser assumes all references in img tags are images, and therefore do not need to be filtered for scripts, this would bypass content filters. In a cross-site scripting attack, the attacker tricks the victim into accessing a URL that uploads a script file with an incorrectly specified MIME type. If the victim's browser switches to the appropriate interpreter without filtering, the attack will execute as a standard XSS attack, possibly revealing the victim's cookies or executing arbitrary script in their browser.
  • Cross-Site Scripting in Attributes
    The attacker inserts commands to perform cross-site scripting (XSS) actions in HTML attributes. Many filters do not adequately sanitize attributes against the presence of potentially dangerous commands even if they adequately sanitize tags. For example, dangerous expressions could be inserted into a style attribute in an anchor tag, resulting in the execution of malicious code when the resulting page is rendered. If a victim is tricked into viewing the rendered page the attack proceeds like a normal XSS attack, possibly resulting in the loss of sensitive cookies or other malicious activities.
  • Cross-Site Scripting via Encoded URI Schemes
    An attack of this type exploits the ability of most browsers to interpret "data", "javascript" or other URI schemes as client-side executable content placeholders. This attack consists of passing a malicious URI in an anchor tag HREF attribute or any other similar attributes in other HTML tags. Such malicious URI contains, for example, a base64 encoded HTML content with an embedded cross-site scripting payload. The attack is executed when the browser interprets the malicious content i.e., for example, when the victim clicks on the malicious link.
  • Cross-Site Scripting Using Doubled Characters, e.g. %3C%3Cscript
    The attacker bypasses input validation by using doubled characters in order to perform a cross-site scripting attack. Some filters fail to recognize dangerous sequences if they are preceded by repeated characters. For example, by doubling the < before a script command, (<<script or %3C%3script using URI encoding) the filters of some web applications may fail to recognize the presence of a script tag. If the targeted server is vulnerable to this type of bypass, the attacker can create a crafted URL or other trap to cause a victim to view a page on the targeted server where the malicious content is executed, as per a normal XSS attack.
  • Cross-Site Scripting Using Flash
    An attacker injects malicious script to global parameters in a Flash movie via a crafted URL. The malicious script is executed in the context of the Flash movie. As such, this is a form of Cross-Site Scripting (XSS), but the abilities granted to the Flash movie make this attack more flexible.
  • Cross-Site Scripting with Masking through Invalid Characters in Identifiers
    The attacker inserts invalid characters in identifiers to bypass application filtering of input. Filters may not scan beyond invalid characters but during later stages of processing content that follows these invalid characters may still be processed. This allows the attacker to sneak prohibited commands past filters and perform normally prohibited operations. Invalid characters may include null, carriage return, line feed or tab in an identifier. Successful bypassing of the filter can result in a XSS attack, resulting in the disclosure of web cookies or possibly other results.
  • Embedding Scripts in HTTP Query Strings
    A variant of cross-site scripting called "reflected" cross-site scripting, the HTTP Query Strings attack consists of passing a malicious script inside an otherwise valid HTTP request query string. This is of significant concern for sites that rely on dynamic, user-generated content such as bulletin boards, news sites, blogs, and web enabled administration GUIs. The malicious script may steal session data, browse history, probe files, or otherwise execute attacks on the client side. Once the attacker has prepared the malicious HTTP query it is sent to a victim user (perhaps by email, IM, or posted on an online forum), who clicks on a normal looking link that contains a poison query string. This technique can be made more effective through the use of services like http://tinyurl.com/, which makes very small URLs that will redirect to very large, complex ones. The victim will not know what he is really clicking on.
  • Simple Script Injection
    An attacker embeds malicious scripts in content that will be served to web browsers. The goal of the attack is for the target software, the client-side browser, to execute the script with the users' privilege level. An attack of this type exploits a programs' vulnerabilities that are brought on by allowing remote hosts to execute code and scripts. Web browsers, for example, have some simple security controls in place, but if a remote attacker is allowed to execute scripts (through injecting them in to user-generated content like bulletin boards) then these controls may be bypassed. Further, these attacks are very difficult for an end user to detect.
  • AJAX Fingerprinting
    This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. In many XSS attacks the attacker must get a "hole in one" and successfully exploit the vulnerability on the victim side the first time, once the client is redirected the attacker has many chances to engage in follow on probes, but there is only one first chance. In a widely used web application this is not a major problem because 1 in a 1,000 is good enough in a widely used application. A common first step for an attacker is to footprint the environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on.
  • Embedding Script (XSS) in HTTP Headers
    An attack of this type exploits web applications that generate web content, such as links in a HTML page, based on unvalidated or improperly validated data submitted by other actors. XSS in HTTP Headers attacks target the HTTP headers which are hidden from most users and may not be validated by web applications.
  • XSS in IMG Tags
    Image tags are an often overlooked, but convenient, means for a Cross Site Scripting attack. The attacker can inject script contents into an image (IMG) tag in order to steal information from a victim's browser and execute malicious scripts.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
NONE PARTIAL NONE
nessus via4
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_DB0C4B00A24C11E29601000D601460A4.NASL
    description Ruby on Rails team reports : Rails versions 3.2.13 has been released. This release contains important security fixes. It is recommended users upgrade as soon as possible. Four vulnerabilities have been discovered and fixed : - (CVE-2013-1854) Symbol DoS vulnerability in Active Record - (CVE-2013-1855) XSS vulnerability in sanitize_css in Action Pack - (CVE-2013-1856) XML Parsing Vulnerability affecting JRuby users - (CVE-2013-1857) XSS Vulnerability in the `sanitize` helper of Ruby on Rails
    last seen 2019-02-21
    modified 2018-11-23
    plugin id 65937
    published 2013-04-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=65937
    title FreeBSD : rubygem-rails -- multiple vulnerabilities (db0c4b00-a24c-11e2-9601-000d601460a4)
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-2655.NASL
    description Several cross-site-scripting and denial of service vulnerabilities were discovered in Ruby on Rails, a Ruby framework for web application development.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 65727
    published 2013-03-29
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=65727
    title Debian DSA-2655-1 : rails - several vulnerabilities
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2013-0698.NASL
    description Updated rubygem-actionpack and ruby193-rubygem-actionpack packages that fix two security issues are now available for Red Hat OpenShift Enterprise 1.1.3. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section. Ruby on Rails is a model-view-controller (MVC) framework for web application development. Action Pack implements the controller and the view components. Two cross-site scripting (XSS) flaws were found in rubygem-actionpack and ruby193-rubygem-actionpack. A remote attacker could use these flaws to conduct XSS attacks against users of an application using rubygem-actionpack or ruby193-rubygem-actionpack. (CVE-2013-1855, CVE-2013-1857) Red Hat would like to thank Ruby on Rails upstream for reporting these issues. Upstream acknowledges Charlie Somerville as the original reporter of CVE-2013-1855, and Alan Jenkins as the original reporter of CVE-2013-1857. Users of Red Hat OpenShift Enterprise 1.1.3 are advised to upgrade to these updated packages, which correct these issues.
    last seen 2019-02-21
    modified 2019-02-06
    plugin id 119434
    published 2018-12-06
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=119434
    title RHEL 6 : rubygem-actionpack and ruby193-rubygem-actionpack (RHSA-2013:0698)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201412-28.NASL
    description The remote host is affected by the vulnerability described in GLSA-201412-28 (Ruby on Rails: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in Ruby on Rails. Please review the CVE identifiers referenced below for details. Impact : A remote attacker could execute arbitrary code or cause a Denial of Service condition. Furthermore, a remote attacker may be able to execute arbitrary SQL commands, change parameter names for form inputs and make changes to arbitrary records in the system, bypass intended access restrictions, render arbitrary views, inject arbitrary web script or HTML, or conduct cross-site request forgery (CSRF) attacks. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-12-05
    plugin id 79981
    published 2014-12-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=79981
    title GLSA-201412-28 : Ruby on Rails: Multiple vulnerabilities
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2013-4214.NASL
    description Fix for CVE-2013-1855 and CVE-2013-1857. Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-05
    plugin id 65755
    published 2013-04-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=65755
    title Fedora 18 : rubygem-actionpack-3.2.8-3.fc18 (2013-4214)
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_SECUPD2013-002.NASL
    description The remote host is running a version of Mac OS X 10.6 or 10.7 that does not have Security Update 2013-002 applied. This update contains numerous security-related fixes for the following components : - CoreMedia Playback (10.7 only) - Directory Service (10.6 only) - OpenSSL - QuickDraw Manager - QuickTime - Ruby (10.6 only) - SMB (10.7 only)
    last seen 2019-02-21
    modified 2018-07-14
    plugin id 66809
    published 2013-06-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=66809
    title Mac OS X Multiple Vulnerabilities (Security Update 2013-002)
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2014-1863.NASL
    description Updated Subscription Asset Manager 1.4 packages that fix multiple security issues are now available. Red Hat Product Security has rated this update as having Important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section. Red Hat Subscription Asset Manager acts as a proxy for handling subscription information and software updates on client machines. Red Hat Subscription Asset Manager is built on Ruby on Rails, a model-view-controller (MVC) framework for web application development. Action Pack implements the controller and the view components. A directory traversal flaw was found in the way Ruby on Rails handled wildcard segments in routes with implicit rendering. A remote attacker could use this flaw to retrieve arbitrary local files accessible to a Ruby on Rails application using the aforementioned routes via a specially crafted request. (CVE-2014-0130) A flaw was found in the way Ruby on Rails handled hashes in certain queries. A remote attacker could use this flaw to perform a denial of service (resource consumption) attack by sending specially crafted queries that would result in the creation of Ruby symbols, which were never garbage collected. (CVE-2013-1854) Two cross-site scripting (XSS) flaws were found in Action Pack. A remote attacker could use these flaws to conduct XSS attacks against users of an application using Action Pack. (CVE-2013-1855, CVE-2013-1857) It was discovered that the internationalization component of Ruby on Rails could, under certain circumstances, return a fallback HTML string that contained user input. A remote attacker could possibly use this flaw to perform a reflective cross-site scripting (XSS) attack by providing a specially crafted input to an application using the aforementioned component. (CVE-2013-4491) A denial of service flaw was found in the header handling component of Action View. A remote attacker could send strings in specially crafted headers that would be cached indefinitely, which would result in all available system memory eventually being consumed. (CVE-2013-6414) It was found that the number_to_currency Action View helper did not properly escape the unit parameter. An attacker could use this flaw to perform a cross-site scripting (XSS) attack on an application that uses data submitted by a user in the unit parameter. (CVE-2013-6415) Red Hat would like to thank Ruby on Rails upstream for reporting these issues. Upstream acknowledges Ben Murphy as the original reporter of CVE-2013-1854, Charlie Somerville as the original reporter of CVE-2013-1855, Alan Jenkins as the original reporter of CVE-2013-1857, Peter McLarnan as the original reporter of CVE-2013-4491, Toby Hsieh as the original reporter of CVE-2013-6414, and Ankit Gupta as the original reporter of CVE-2013-6415. All Subscription Asset Manager users are advised to upgrade to these updated packages, which contain backported patches to correct these issues.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 79326
    published 2014-11-19
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=79326
    title RHEL 6 : Subscription Asset Manager (RHSA-2014:1863)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2013-4199.NASL
    description Fix for CVE-2013-1855 and CVE-2013-1857. Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-05
    plugin id 65752
    published 2013-04-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=65752
    title Fedora 17 : rubygem-actionpack-3.0.11-9.fc17 (2013-4199)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2013-324.NASL
    description Changes in rubygem-actionpack-2_3 : - add 2 patches to fix security issues : - bug-809935_2-3-css_sanitize.patch: CVE-2013-1855: rubygem-actionpack*: XSS vulnerability in sanitize_css in Action Pack (bnc#809935) - bug-809940_2-3-sanitize_protocol.patch: CVE-2013-1857: rubygem-actionpack*: XSS Vulnerability in the `sanitize` helper of Ruby on Rails (bnc#809940)
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 74968
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=74968
    title openSUSE Security Update : rubygem-actionpack-2_3 (openSUSE-SU-2013:0662-1)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2013-329.NASL
    description Changes in rubygem-actionpack-3_2 : - add 2 patches to fix security issues : - bug-809935_3-2-css_sanitize.patch: CVE-2013-1855: rubygem-actionpack*: XSS vulnerability in sanitize_css in Action Pack (bnc#809935) - bug-809940_3-2-sanitize_protocol.patch: CVE-2013-1857: rubygem-actionpack*: XSS Vulnerability in the `sanitize` helper of Ruby on Rails (bnc#809940)
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 74972
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=74972
    title openSUSE Security Update : rubygem-actionpack-3_2 (openSUSE-SU-2013:0661-1)
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_SERVER_3_0.NASL
    description The remote Mac OS X host has a version of OS X Server installed that is prior to 3.0. It is, therefore, affected by the following vulnerabilities : - A denial of service vulnerability exists in the included JSON Ruby Gem, which can be abused to exhaust all available memory resources. (CVE-2013-0269) - Multiple cross-site scripting vulnerabilities exist in the included Ruby on Rails software. (CVE-2013-1854 / CVE-2013-1855 / CVE-2013-1856 / CVE-2013-1857) - A buffer overflow exists in the included FreeRADIUS software that can be triggered when parsing the 'not after' timestamp in a client certificate when using TLS-based EAP methods. (CVE-2012-3547) - A logic issue exists whereby the RADIUS service could choose an incorrect certificate from a list of configured certificates.
    last seen 2019-02-21
    modified 2018-07-14
    plugin id 70590
    published 2013-10-24
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=70590
    title Mac OS X : OS X Server < 3.0 Multiple Vulnerabilities
redhat via4
advisories
  • rhsa
    id RHSA-2013:0698
  • rhsa
    id RHSA-2014:1863
refmap via4
apple
  • APPLE-SA-2013-06-04-1
  • APPLE-SA-2013-10-22-5
confirm
mlist [rubyonrails-security] 20130318 [CVE-2013-1857] XSS Vulnerability in the `sanitize` helper of Ruby on Rails
suse
  • openSUSE-SU-2013:0661
  • openSUSE-SU-2013:0662
  • openSUSE-SU-2014:0019
Last major update 28-09-2015 - 11:56
Published 19-03-2013 - 18:55
Last modified 22-04-2019 - 13:48
Back to Top