ID CVE-2014-1695
Summary Cross-site scripting (XSS) vulnerability in Open Ticket Request System (OTRS) 3.1.x before 3.1.20, 3.2.x before 3.2.15, and 3.3.x before 3.3.5 allows remote attackers to inject arbitrary web script or HTML via a crafted HTML email.
References
Vulnerable Configurations
  • Open Ticket Request System (OTRS) 3.3.0
    cpe:2.3:a:otrs:otrs:3.3.0
  • Open Ticket Request System (OTRS) 3.3.0 beta1
    cpe:2.3:a:otrs:otrs:3.3.0:beta1
  • Open Ticket Request System (OTRS) 3.3.0 beta2
    cpe:2.3:a:otrs:otrs:3.3.0:beta2
  • Open Ticket Request System (OTRS) 3.3.0 beta3
    cpe:2.3:a:otrs:otrs:3.3.0:beta3
  • Open Ticket Request System (OTRS) 3.3.0 beta4
    cpe:2.3:a:otrs:otrs:3.3.0:beta4
  • Open Ticket Request System (OTRS) 3.3.0 beta5
    cpe:2.3:a:otrs:otrs:3.3.0:beta5
  • Open Ticket Request System (OTRS) 3.3.0 release candidate 1
    cpe:2.3:a:otrs:otrs:3.3.0:rc1
  • Open Ticket Request System (OTRS) 3.3.1
    cpe:2.3:a:otrs:otrs:3.3.1
  • Open Ticket Request System (OTRS) 3.3.2
    cpe:2.3:a:otrs:otrs:3.3.2
  • Open Ticket Request System (OTRS) 3.3.3
    cpe:2.3:a:otrs:otrs:3.3.3
  • Open Ticket Request System (OTRS) 3.3.4
    cpe:2.3:a:otrs:otrs:3.3.4
  • Open Ticket Request System (OTRS) 3.2.0
    cpe:2.3:a:otrs:otrs:3.2.0
  • Open Ticket Request System (OTRS) 3.2.0 beta1
    cpe:2.3:a:otrs:otrs:3.2.0:beta1
  • Open Ticket Request System (OTRS) 3.2.0 beta2
    cpe:2.3:a:otrs:otrs:3.2.0:beta2
  • Open Ticket Request System (OTRS) 3.2.0 beta3
    cpe:2.3:a:otrs:otrs:3.2.0:beta3
  • Open Ticket Request System (OTRS) 3.2.0 beta4
    cpe:2.3:a:otrs:otrs:3.2.0:beta4
  • Open Ticket Request System (OTRS) 3.2.0 beta5
    cpe:2.3:a:otrs:otrs:3.2.0:beta5
  • Open Ticket Request System (OTRS) 3.2.0 release candidate 1
    cpe:2.3:a:otrs:otrs:3.2.0:rc1
  • Open Ticket Request System (OTRS) 3.2.1
    cpe:2.3:a:otrs:otrs:3.2.1
  • Open Ticket Request System (OTRS) 3.2.10
    cpe:2.3:a:otrs:otrs:3.2.10
  • Open Ticket Request System (OTRS) 3.2.14
    cpe:2.3:a:otrs:otrs:3.2.14
  • Open Ticket Request System (OTRS) 3.2.2
    cpe:2.3:a:otrs:otrs:3.2.2
  • Open Ticket Request System (OTRS) 3.2.3
    cpe:2.3:a:otrs:otrs:3.2.3
  • Open Ticket Request System (OTRS) 3.2.4
    cpe:2.3:a:otrs:otrs:3.2.4
  • Open Ticket Request System (OTRS) 3.2.5
    cpe:2.3:a:otrs:otrs:3.2.5
  • Open Ticket Request System (OTRS) 3.2.6
    cpe:2.3:a:otrs:otrs:3.2.6
  • Open Ticket Request System (OTRS) 3.2.7
    cpe:2.3:a:otrs:otrs:3.2.7
  • Open Ticket Request System (OTRS) 3.2.8
    cpe:2.3:a:otrs:otrs:3.2.8
  • Open Ticket Request System (OTRS) 3.2.9
    cpe:2.3:a:otrs:otrs:3.2.9
  • Open Ticket Request System (OTRS) 3.1.0
    cpe:2.3:a:otrs:otrs:3.1.0
  • Open Ticket Request System (OTRS) 3.1.1
    cpe:2.3:a:otrs:otrs:3.1.1
  • Open Ticket Request System (OTRS) 3.1.10
    cpe:2.3:a:otrs:otrs:3.1.10
  • Open Ticket Request System (OTRS) 3.1.11
    cpe:2.3:a:otrs:otrs:3.1.11
  • Open Ticket Request System (OTRS) 3.1.13
    cpe:2.3:a:otrs:otrs:3.1.13
  • Open Ticket Request System (OTRS) 3.1.14
    cpe:2.3:a:otrs:otrs:3.1.14
  • Open Ticket Request System (OTRS) 3.1.15
    cpe:2.3:a:otrs:otrs:3.1.15
  • Open Ticket Request System (OTRS) 3.1.16
    cpe:2.3:a:otrs:otrs:3.1.16
  • Open Ticket Request System (OTRS) 3.1.17
    cpe:2.3:a:otrs:otrs:3.1.17
  • Open Ticket Request System (OTRS) 3.1.18
    cpe:2.3:a:otrs:otrs:3.1.18
  • Open Ticket Request System (OTRS) 3.1.19
    cpe:2.3:a:otrs:otrs:3.1.19
  • Open Ticket Request System (OTRS) 3.1.2
    cpe:2.3:a:otrs:otrs:3.1.2
  • Open Ticket Request System (OTRS) 3.1.3
    cpe:2.3:a:otrs:otrs:3.1.3
  • Open Ticket Request System (OTRS) 3.1.4
    cpe:2.3:a:otrs:otrs:3.1.4
  • Open Ticket Request System (OTRS) 3.1.5
    cpe:2.3:a:otrs:otrs:3.1.5
  • Open Ticket Request System (OTRS) 3.1.6
    cpe:2.3:a:otrs:otrs:3.1.6
  • Open Ticket Request System (OTRS) 3.1.7
    cpe:2.3:a:otrs:otrs:3.1.7
  • Open Ticket Request System (OTRS) 3.1.8
    cpe:2.3:a:otrs:otrs:3.1.8
  • Open Ticket Request System (OTRS) 3.1.9
    cpe:2.3:a:otrs:otrs:3.1.9
CVSS
Base: 4.3 (as of 13-10-2015 - 12:00)
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
exploit-db via4
description OTRS < 3.1.x & < 3.2.x & < 3.3.x - Stored Cross-Site Scripting (XSS). CVE-2014-1695. Webapps exploit for php platform
file exploits/php/webapps/36842.pl
id EDB-ID:36842
last seen 2016-02-04
modified 2015-04-27
platform php
port
published 2015-04-27
reporter Adam Ziaja
source https://www.exploit-db.com/download/36842/
title OTRS < 3.1.x & < 3.2.x & < 3.3.x - Stored Cross-Site Scripting XSS
type webapps
nessus via4
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DLA-1119.NASL
    description An attacker who is logged into OTRS, a Ticket Request System, as an agent with write permissions for statistics can inject arbitrary code into the system. This can lead to serious problems like privilege escalation, data loss, and denial of service. This issue is also known as CVE-2017-14635 and is resolved by upgrading to the latest upstream release of OTRS3. ****IMPORTANT UPGRADE NOTES**** =============================== This update requires manual intervention. We strongly recommend to backup all files and databases before upgrading. If you use the MySQL backend you should read Debian bug report #707075 and the included README.Debian file which will provide further information. If you discover that the maintenance mode is still activated after the update, we recommend to remove /etc/otrs/maintenance.html and /var/lib/otrs/httpd/htdocs/maintenance.html which will resolve the issue . In addition the following security vulnerabilities were also addressed : CVE-2014-1695 Cross-site scripting (XSS) vulnerability in OTRS allows remote attackers to inject arbitrary web script or HTML via a crafted HTML email CVE-2014-2553 Cross-site scripting (XSS) vulnerability in OTRS allows remote authenticated users to inject arbitrary web script or HTML via vectors related to dynamic fields CVE-2014-2554 OTRS allows remote attackers to conduct clickjacking attacks via an IFRAME element For Debian 7 'Wheezy', these problems have been fixed in version 3.3.18-1~deb7u1. We recommend that you upgrade your otrs2 packages. NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2018-09-02
    modified 2018-07-09
    plugin id 103577
    published 2017-10-02
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=103577
    title Debian DLA-1119-1 : otrs2 security update
  • NASL family Mandriva Local Security Checks
    NASL id MANDRIVA_MDVSA-2014-054.NASL
    description Updated otrs package fixes security vulnerability : An attacker could send a specially prepared HTML email to OTRS. If he can then trick an agent into following a special link to display this email, JavaScript code would be executed (CVE-2014-1695).
    last seen 2018-09-01
    modified 2018-07-19
    plugin id 73001
    published 2014-03-14
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73001
    title Mandriva Linux Security Advisory : otrs (MDVSA-2014:054)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2014-202.NASL
    description The OTRS ticket system was updated to 3.1.20 / 3.2.15 : On openSUSE 12.3 it was updated to 3.1.20: (fix for OSA-2014-03, CVE-2014-1695) - Improved HTML filter. - 3.1.19 2014-01-28 - Fixed bug#10158 - Missing quoting in State::StateGetStatesByType(). - Fixed bug#10099 - Missing challenge token checks on customer interface. - Fixed bug#8489 - setting Tickets per page resets AgentTicketQueue. - Fixed bug#9661 - Useless code in DynamicField backend. - Fixed bug#9622 - Actions in Small ticket overview don't work when cookies are turned off. - Fixed bug#9541 - Package manager cannot use https proxy. - Fixed bug#9594 - No auto-reply sent with multiple From addresses in AgentTicketPhone on PostgreSQL and Oracle. - Fixed bug#3434 - Validity of search time frame not checked by OTRS. - Fixed bug#9596 - On merge and bounce screens is confusing when fill or not 'To', 'Subject' and 'Body' fields. - Fixed bug#9595 - Incomplete page reload handling in merge and bounce. - Fixed bug#3007 - CheckMXRecord and CheckEmailAddresses have no effect on AgentTicketBounce. - Fixed bug#9512 - Database error for invalid date in AgentTicketSearch. - Fixed bug#8835 - No article found for TicketID when showing group tickets - Fixed bug#9583 - Dynamic Fields of type Date have timestamp in notifications. - Fixed bug#9579 - SOAP Serializer used in Kernel/GenericInterface/Transport/ HTTP/SOAP.pm does not correctly set namespace. - Fixed bug#7359 - Setting pending states via generic agent does not set pending time. - Fixed bug#8380 - Middle name not displayed in AdminCustomerUser. - Fixed bug#9576 - GI TicketSearch Date and Date/Time dynamic fields are ignored. - Changed Dynamic Field SearchFieldParameterBuild() API, LayoutObject is now optional. - Fixed bug#9573 - Date and DateTime dynamic fields not considered in GenericAgent Jobs. On openSUSE 13.1 it was updated to 3.2.15: (fix for OSA-2014-03, CVE-2014-1695) - Improved HTML filter. - Fixed bug#10207 - DynamicField Search-Function in CustomerFrontend is not working. - Followup for bug#9011 - New value after value mapping can't be 0. - Fixed bug#10214 - Value '0' for DynamicsFields prevents TicketCreation. - Fixed bug#9616 - Too long activities and transitions are not displayed correctly. - Fixed bug#10212 - My tickets & Company tickets in 3.3.4. - Fixed bug#10205 - GenericInterface: Mandatory TimeUnits can't be 0. - Fixed bug#10196 - Ticket merge action does not notify the owner of the existing ticket. - Fixed bug#9692 - On PhoneOutbound articles, the FROM field shows Customer ID instead Agent ID. - Fixed bug#10189 - ProcessManagement: Use article subject if no ticket title is set. - Fixed bug#9654 - TicketUpdate operation doesn't work when authenticated as a customer. - Fixed bug#10137 - Generic interface TicketCreate operation doesn't work when authenticated as a customer. - 3.2.14 - Fixed bug#10172 - Can't create process tickets with disabled richtext. - Fixed bug#10121 - QQMails break in OTRS. - Fixed bug#10158 - Missing quoting in State::StateGetStatesByType(). - Fixed bug#8969 - FAQ module Language files installation fails (Kernel/Language permissions). - Fixed bug#9959 - & breaks ExpandCustomerName. - Fixed bug#10099 - Missing challenge token checks on customer interface. - Fixed bug#10103 - ArticleTypeID is always undef in AgentTicketCompose. - Added functionality to disable access to tickets of other customers with the same customer company in customer interface. - Fixed bug#9650 - Special character in customer id breaks Open Tickets in AgentTicketZoom. - Fixed bug#9723 - TicketAccountedTime stat does not run on Oracle with many tickets - Fixed bug#10077 - regular expressions in postmaster filter return 1 if no regex match. - Fixed bug#10070 - Wrong error message if Transition contains no transition actions.
    last seen 2018-11-13
    modified 2018-11-10
    plugin id 75286
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=75286
    title openSUSE Security Update : otrs (openSUSE-SU-2014:0360-1)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_70B72A529E5411E3BABE60A44C524F57.NASL
    description The OTRS Project reports : An attacker could send a specially prepared HTML email to OTRS. If he can then trick an agent into following a special link to display this email, JavaScript code would be executed.
    last seen 2018-11-13
    modified 2018-11-10
    plugin id 72696
    published 2014-02-26
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=72696
    title FreeBSD : otrs -- XSS Issue (70b72a52-9e54-11e3-babe-60a44c524f57)
packetstorm via4
data source https://packetstormsecurity.com/files/download/131654/otrs31x-xss.txt
id PACKETSTORM:131654
last seen 2016-12-05
published 2015-04-27
reporter Adam Ziaja
source https://packetstormsecurity.com/files/131654/OTRS-3.x-Cross-Site-Scripting.html
title OTRS 3.x Cross Site Scripting
refmap via4
bid 65844
confirm https://www.otrs.com/security-advisory-2014-03-xss-issue
misc
osvdb 103781
secunia 57018
suse openSUSE-SU-2014:0360
Last major update 13-10-2015 - 12:35
Published 28-02-2014 - 19:01
Back to Top