Vulnerabilities > CVE-2008-1009 - Cross-Site Scripting vulnerability in Apple Safari

047910
CVSS 4.3 - MEDIUM
Attack vector
NETWORK
Attack complexity
MEDIUM
Privileges required
NONE
Confidentiality impact
NONE
Integrity impact
PARTIAL
Availability impact
NONE
network
apple
CWE-79
nessus

Summary

Cross-site scripting (XSS) vulnerability in WebCore, as used in Apple Safari before 3.1, allows remote attackers to inject arbitrary JavaScript by modifying the history object.

Common Attack Pattern Enumeration and Classification (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.

Nessus

NASL familyMacOS X Local Security Checks
NASL idMACOSX_SAFARI31.NASL
descriptionThe version of Apple Safari installed on the remote host is older than version 3.1. The remote version of this software contains several security vulnerabilities that may allow an attacker to execute arbitrary code or launch a cross-site scripting attack on the remote host. To exploit these flaws, an attacker would need to lure a victim into visiting a rogue website or opening a malicious HTML file.
last seen2020-04-30
modified2008-03-18
plugin id31604
published2008-03-18
reporterThis script is Copyright (C) 2008-2020 and is owned by Tenable, Inc. or an Affiliate thereof.
sourcehttps://www.tenable.com/plugins/nessus/31604
titleMac OS X : Apple Safari < 3.1

Seebug

bulletinFamilyexploit
descriptionBUGTRAQ ID: 28290 CVE(CAN) ID: CVE-2008-1011,CVE-2008-1010,CVE-2008-1009,CVE-2008-1008,CVE-2008-1007,CVE-2008-1006,CVE-2008-1005,CVE-2008-1004,CVE-2008-1003,CVE-2008-1002,CVE-2008-1001,CVE-2008-0050 Safari是苹果家族操作系统默认所捆绑的WEB浏览器。 Safari的3.1版修复了多个安全漏洞,具体如下: CVE-2008-0050 恶意的HTTPS代理服务器可能在502 Bad Gateway错误中向CFNetwork返回任意数据,这可能允许欺骗安全的站点。 CVE-2008-1001 Safari的错误页面中存在跨站脚本漏洞,如果用户受骗打开了恶意的URL的话,就可能导致泄露敏感信息。 CVE-2008-1002 javascript: URL处理中存在跨行脚本漏洞,如果用户受骗访问了恶意网页的话,就可能导致在其他站点的安全环境中执行JavaScript。 CVE-2008-1003 处理设置有document.domain属性的网页的方式存在漏洞,如果站点设置了document.domain属性,或在有相同document.domain的HTTP和HTTPS的网站之间,这可能导致跨站脚本攻击。 CVE-2008-1004 Web Inspector中的漏洞可能允许正在检查的页面通过注入在其他域中运行的脚本提升权限并读取用户的文件系统。 CVE-2008-1005 正常情况下网页的口令字段是隐藏的,以防泄露。Kotoeri输入法使用中的漏洞导致在请求逆向转换的时候暴露口令字段内容。 CVE-2008-1006 window.open()函数可能导致将网页的安全环境更改为调用者的安全环境。如果用户受骗访问了恶意网页的话,就可能允许在用户安全环境中执行任意脚本。 CVE-2008-1007 没有对Java applet强制帧导航策略,如果用户受骗访问了特制网页的话,就可能允许攻击者使用Java通过跨站脚本攻击获得权限提升。 CVE-2008-1008 Safari处理document.domain属性的方式存在跨站脚本漏洞,诱骗用户访问特制的网页可能导致泄露敏感信息。 CVE-2008-1009 处理历史对象时存在JavaScript注入漏洞,允许帧在同一网页所加载的所有其他帧中设置历史对象属性。攻击者可以利用这个漏洞注入可以在其他帧安全环境中运行的JavaScript,导致跨站脚本。 CVE-2008-1010 WebKit处理JavaScript正则表达式的方式存在缓冲区溢出,如果诱骗用户访问了恶意网页就会导致应用程序意外终止或执行任意代码。 CVE-2008-1011 WebKit中的跨站脚本漏洞允许在其他帧的安全环境中调用帧的方式例程。如果用户受骗访问了恶意网页的话,就会导致泄露敏感信息。 Apple Safari &lt; 3.1 Apple ----- 目前厂商已经发布了升级补丁以修复这个安全问题,请到厂商的主页下载: <a href=http://wsidecar.apple.com/cgi-bin/nph-reg3rdpty2.pl/product=18166&amp;cat=59&amp;platform=osx&amp;method=sa/ target=_blank>http://wsidecar.apple.com/cgi-bin/nph-reg3rdpty2.pl/product=18166&amp;cat=59&amp;platform=osx&amp;method=sa/</a>
idSSV:3057
last seen2017-11-19
modified2008-03-20
published2008-03-20
reporterRoot
titleApple Safari 3.1之前版本多个安全漏洞