CDM-CYBER-DEFENSE-eMAGAZINE-March-2019

More documents

Recommendations

Info

Cross-site Scripting Is an Underrated Vulnerability Find out Why Cross-site Scripting (XSS) is an underrated vulnerability and how this article will transform your thought. By Pedro Tavares, Founder of CSIRT.UBI & Cyber Security Blog seguranca-informatica.pt Cybersecurity attacks are an enormous challenge from the point-of-view of people, organization and nations. Also called cyberattacks, they represent a malicious attempt by an individual or organization to breach the information system of another individual or organization. For many years, an injection vulnerability has positioned itself in OWASP's TOP 10 vulnerabilities — Cross-site scripting, also known as XSS. These type of attacks work by injecting some piece of code into a benign and trusted web application. It occur when an adversary uses a web application to send malicious code, typically in the form of a browser side script, to different end users. The flaws that can be exploited by adversaries are quite widespread and occur anywhere a web application uses input from a user within the output it generates without validating or encoding it. This article aims to give a lot of things we can do with XSS — an underrated vulnerability. The Art of XSS The principle of XSS is always execute malicious JavaScript code in the victim’s browser. There are different ways of achieving this goal, and they are often divided into three types, namely: Persistent XSS: Malicious payload originates from the website's database. Reflected XSS: Malicious payload originates from the victim's request. DOM-based XSS: The vulnerability is in the client-side code rather than the server-side code.
XSS and the Hackers’ Inspiration XSS is and underrated vulnerability. In fact, there are three good reasons for that: (i) it’s a client side vulnerability, (ii) many white hats just need that popup for proof-of-concepts, and (iii), most of the black’s hats don’t know enough JavaScript to make much money with XSS. XSS is a powerful attack vector to inject malicious payloads and can be used to impersonate something as well. There are a lot of things that we can do with XSS. Next, a list with possible scenarios used by adversaries in real attacks are presented. Ad-Jacking: Adversaries can inject its own ads in a legitimate website to make money easily and based on a persistent XSS. Click-Jacking: Hidden overlays can be created in a website to hijack victim clicks and to perform malicious actions such as redirects to login pages and exhibit false payment forms. Session Hijacking: HTTP cookies can be accessed via JavaScript whenever the HTTP ONLY flag is not present in the cookies. Content Spoofing: JavaScript is very powerful. In this way, an adversary can modify a page with desired content as the JavaScript has full access to client side code. Credential Harvesting: Victims put their own credentials in a fancy pop-up created by adversaries with the goal of harvest their credentials. Forced Downloads: There are several application vulnerabilities that hackers are leveraging. One of the most popular example is the Flash Player. Adversaries can force the download from a trusted website that the victim is visiting. Crypto Mining: Adversaries can use the victim’s CPU power to mine cryptocurrency without its consent and knowledge. Bypassing CSRF protection: Adversaries can make POST requests with JavaScript. They can collect and submit a CSRF token and steal data or even execute critical operations in a third-party service. Keylogging: Anything that victim’s type in their keyboard can be harvested. Recording Audio: - It requires authorization from the user but adversaries can access microphones. This is possible from HTML5 and JavaScript. Taking pictures: Adversaries can take pictures from the victim’s webcam (this requires authorization from the user). Geo-location: That requires authorization from the user but adversaries can access victim’s geolocation.
Page 1 and 2: Data Breaches: Beyond Exposing Iden
Page 3 and 4: CONTENTS (cont') Prioritizing Secur
Page 5: @CYBERDEFENSEMAG CYBER DEFENSE eMAG
Page 22 and 23: Data Breaches: Beyond Exposing Iden
Page 24 and 25: About the Author Kem Gay is an Inte
Page 26 and 27: Rip Off the Band-Aid This leaves us
Page 28 and 29: Why Biometric Data Use Poses Unique
Page 30 and 31: • DNA Kits: If you purchased or u
Page 32 and 33: How to be Workforce Ready and Stand
Page 34 and 35: Maximiliano Gigli, a third-year cyb
Page 36 and 37: Interestingly, the two groups diffe
Page 40 and 41: Stealing HTML5 web storage data: HT
Page 42 and 43: Cybersecurity in New York City, the
Page 44 and 45: A boom in cybersecurity startups se
Page 46 and 47: illion risks and threats among its
Page 48 and 49: Some Important Developments in the
Page 50 and 51: About the Author Sharmistha Sarkar
Page 52 and 53: employees to contractors and sub-co
Page 54 and 55: The Internet of Things Engineering
Page 56 and 57: About The Author Milica D. Djekic i
Page 58 and 59: kind. Many of them require some kin
Page 60 and 61: 2019 Risks in Focus: Cyber Incident
Page 62 and 63: However, the past year has also wit
Page 64 and 65: Why Insider Threats Are One of the
Page 66 and 67: Unlike with outside security threat
Page 68 and 69: Organizations will also frequently
Page 70 and 71: The US Must Catch Up to Other Promi
Page 72 and 73: The fact is, the wider internationa
Page 74 and 75: Integrate Compliance and Regulation
Page 76 and 77: Security have and have-nots How org
Page 78 and 79: 1. People Having the right people c
Page 80 and 81: sources (such as syslog’s, Net Fl
Page 82 and 83: Limitations of Current Endpoint Sec
Page 84 and 85: For effective detection, most EDR s
Page 86 and 87: Why Wi-Fi Hacking Will Persist Desp
Page 88 and 89:
About the Author Ryan Orsi is Direc
Page 90 and 91:
questions such as, “Who added a w
Page 92 and 93:
About the Author Josh Paape is an O
Page 94 and 95:
for well-known, repeatable needs fi
Page 96 and 97:
Overcoming Software Security Issues
Page 98 and 99:
Implementing Security Checks at Str
Page 100 and 101:
Phishing in the Dark: Employee Secu
Page 102 and 103:
phishing threats. Furthermore, almo
Page 104 and 105:
Unfortunately, once an application
Page 106 and 107:
Software Should Come with a “Nutr
Page 108 and 109:
vulnerabilities. If they find vulne
Page 110 and 111:
I can't get no satisfaction, I can'
Page 112 and 113:
How Organizations Should Choose a L
Page 114 and 115:
load balancers capable of integrati
Page 116 and 117:
SaaS DNS Security: Are you Protecte
Page 118 and 119:
associated with any security event
Page 120 and 121:
120
Page 122 and 123:
122
Page 124 and 125:
124
Page 126 and 127:
126
Page 128 and 129:
128
Page 130 and 131:
130
Page 132 and 133:
132
Page 134 and 135:
134
Page 136 and 137:
136
Page 138 and 139:
138
Page 140 and 141:
140
Page 142 and 143:
142
Page 144 and 145:
144
Page 146 and 147:
146
Page 148 and 149:
148
Page 150 and 151:
We’ve launched http://www.CyberDe
Page 152 and 153:
Marketing and Partnership Opportuni
Page 154 and 155:
Regent University’s Institute for
Page 156 and 157:
156
show all

CDM-CYBER-DEFENSE-eMAGAZINE-March-2019

Create successful ePaper yourself

Delete template?

Save as template?