On Network Attacks
On Network Attacks
On Network Attacks
• On Feb. 28, 2018, GitHub—a popular developer platform—was hit with a sudden
onslaught of traffic that clocked in at 1.35 terabits per second. If that sounds like a lot,
that’s because it is—that amount of traffic is not only massive, it’s record-breaking.
• In 2012, not one, not two, but a whopping six U.S. banks were targeted by a string of
DDoS attacks. The victims were no small-town banks either: They included Bank of America,
JP Morgan Chase, U.S. Bancorp, Citigroup and PNC Bank. The attack was carried out by
hundreds of hijacked servers, which each created peak floods of more than 60 gigabits of
traffic per second.
SQL Injection
• SQL injection has become a common issue with database-driven websites. It occurs
when a malefactor executes a SQL query to the database via the input data from the
client to server. SQL commands are inserted into data-plane input (for example,
instead of the login or password) in order to run predefined SQL commands.
• A successful SQL injection exploit can read sensitive data from the database, modify
(insert, update or delete) database data, execute administration operations (such as
shutdown) on the database, recover the content of a given file, and, in some cases,
issue commands to the operating system.
• SQL injections work mostly if a website uses dynamic SQL. Additionally, SQL injection is
very common with PHP and ASP applications due to the prevalence of older functional
interfaces. J2EE and ASP.NET applications are less likely to have easily exploited SQL
injections because of the nature of the programmatic interfaces available.
SQL Injection ctd.
• For example, a web form on a website might request a user’s account
name and then send it to the database in order to pull up the
associated account information using dynamic SQL like this:
“SELECT * FROM users WHERE account = ‘“ +
userProvidedAccountNumber +”’;”
While this works for users who are properly entering their account
number, it leaves a hole for attackers. For example, if someone decided
to provide an account number of “‘ or ‘1’ = ‘1’”, that would result in a
query string of:
Because ‘1’ = ‘1’ always evaluates to TRUE, the database will return the
data for all users instead of just a single user.
Cross-Site Scripting(XSS)
• XSS attacks use third-party web resources to run scripts in the victim’s web
browser or scriptable application. Specifically, the attacker injects a payload
with malicious JavaScript into a website’s database. When the victim requests a
page from the website, the website transmits the page, with the attacker’s
payload as part of the HTML body, to the victim’s browser, which executes the
malicious script.
• For example, it might send the victim’s cookie to the attacker’s server, and the
attacker can extract it and use it for session hijacking. The most dangerous
consequences occur when XSS is used to exploit additional vulnerabilities. These
vulnerabilities can enable an attacker to not only steal cookies, but also log key
strokes, capture screenshots, discover and collect network information, and
remotely access and control the victim’s machine.
Cross-Site Scripting(XSS)
Eavesdropping Attack
• Eavesdropping attacks occur through the interception of network
traffic. By eavesdropping, an attacker can obtain passwords,
credit card numbers and other confidential information that a
user might be sending over the network. Eavesdropping can be
passive or active:
• Passive eavesdropping — A hacker detects the information by
listening to the message transmission in the network.
• Active eavesdropping — A hacker actively grabs the
information by disguising himself as friendly unit and by sending
queries to transmitters. This is called probing, scanning or
tampering.