Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
| modul:m183:learningunits:lu10:lu10b [2025/12/27 19:30] – angelegt dgaravaldi | modul:m183:learningunits:lu10:lu10b [2025/12/27 21:04] (aktuell) – dgaravaldi | ||
|---|---|---|---|
| Zeile 9: | Zeile 9: | ||
| To distribute the malicious link, a perpetrator typically embeds it into an email or third party website (e.g., in a comment section or in social media). The link is embedded inside an anchor text that provokes the user to click on it, which initiates the XSS request to an exploited website, reflecting the attack back to the user. | To distribute the malicious link, a perpetrator typically embeds it into an email or third party website (e.g., in a comment section or in social media). The link is embedded inside an anchor text that provokes the user to click on it, which initiates the XSS request to an exploited website, reflecting the attack back to the user. | ||
| - | \\ | + | {{: |
| - | ==== Reflected XSS attack example ==== | + | |
| Unlike a stored attack, where the perpetrator must locate a website that allows for permanent injection of malicious scripts, reflected attacks only require that the malicious script be embedded into a link. That being said, in order for the attack to be successful, the user needs to click on the infected link. | Unlike a stored attack, where the perpetrator must locate a website that allows for permanent injection of malicious scripts, reflected attacks only require that the malicious script be embedded into a link. That being said, in order for the attack to be successful, the user needs to click on the infected link. | ||
| Zeile 36: | Zeile 35: | ||
| link into a seemingly harmless email, which he sends to a group of forum users. | link into a seemingly harmless email, which he sends to a group of forum users. | ||
| - | While the sending address and subject line may appear suspect to some, it does not mean that it won’t be clicked on. | + | While the sending address and subject line may appear suspect to some, it does not mean that it won’t be clicked on. In fact, even if only one in every 1,000 recipients of the email click on the link, that still amounts to several dozen infected forum users. They will be taken to the forum’s website, where the malicious script will be reflected back to their browser, enabling the perpetrator to steal their session cookies and hijack their forum accounts. |
| + | |||
| + | \\ | ||
| + | ==== Reflected XSS attack prevention and mitigation ==== | ||
| + | There are several effective methods for preventing and mitigating reflected XSS attacks. First and foremost, from the user’s point-of-view, | ||
| + | |||
| + | * Emails from unknown senders | ||
| + | * A website’s comments section | ||
| + | * Social media feed of unknown users | ||
| + | |||
| + | \\ | ||
| + | ==== Related Topics ==== | ||
| + | [1]: https:// | ||
| - | In fact, even if only one in every 1,000 recipients of the email click on the link, that still amounts to several dozen infected forum users. They will be taken to the forum’s website, where the malicious script will be reflected back to their browser, enabling the perpetrator to steal their session cookies and hijack their forum accounts. | ||