Name of The Faculty: Mrs.M.Akilandeeswari Subject Name & Code: Branch & Department: B.Tech & AI&DS Year & Semester: 2023 / VI Academic Year:2023-24
Name of The Faculty: Mrs.M.Akilandeeswari Subject Name & Code: Branch & Department: B.Tech & AI&DS Year & Semester: 2023 / VI Academic Year:2023-24
Name of The Faculty: Mrs.M.Akilandeeswari Subject Name & Code: Branch & Department: B.Tech & AI&DS Year & Semester: 2023 / VI Academic Year:2023-24
2
TEXTBOOKS
1. Michael T. Simpson, Kent Backman, and James E. Corley, Hands-On Ethical Hacking and
Elsevier, 2013.
3. The Web Application Hacker’s Handbook: Finding and Exploiting Security Flaws, Dafydd
REFERENCES
1. Black Hat Python: Python Programming for Hackers and Pentesters, Justin Seitz , 2014
3
SYLLABUS
COURSE OUTCOMES:
CO2: To gain understanding on different foot printing, reconnaissance and scanning methods.
CO4: To gain knowledge on hacking options available in Web and wireless applications.
•OWASP (www.owasp.org) publishes the Ten Most Critical Web Application Security
Vulnerabilities paper, which has been built into the Payment Card Industry (PCI) Data Security
Standard (DSS).
•In this vulnerability, a Web browser might carry out code sent from a Web site. Attackers can
use a Web application to run a script on the Web browser of the system they’re attacking.
• XSS is one of the easiest types of attacks to perform, which also makes it one of the most
common; attackers simply save the form to their local computers and change the form field
values.
2)Injection flaws:
•Many Web applications pass parameters when accessing an external system. For example, a
Web application that accesses a database server needs to pass logon information to the
database server.
•An attacker can embed malicious code and run a program on the database server or send
malicious code in an HTTP request. Basically, the attacker is tricking the Web application into
running malware or making unauthorized changes to data
•Some Web applications allow users to reference or upload files containing malware.
•If these references or files aren’t checked before the Web application executes them, they can
give attackers complete control of the system
•This vulnerability occurs when information returned via the URL to a user’s Web browser
contains information (references) about files, directories, or database records. By simply
changing the information in the URL, attackers can gain unauthorized access to information.
• For example, a Web application from the IRS with this vulnerability might show your Social
Security number in the URL returned to your Web browser. By changing the SSN in the URL and
sending it back to the Web application, you could then access another person’s information.
•This vulnerability is also known as a one-click or session-riding attack. To send malicious code
to a Web application, the attacker exploits a Web browser that has already been authenticated
and is, therefore, trusted.
• Because the malicious code is coming from a trusted Web browser, it’s normally executed
without being checked or validated. This vulnerability can be extremely dangerous
•If an error occurs during normal operations and isn’t handled correctly, information sent to
users might reveal information attackers can use.
•For example, attackers can take advantage of error messages that reveal what was executed
on the stack or indicate what Web software is used
• To reduce this risk, using strong authentication methods is critical, and credentials must be
kept secret.
•You can also incorporate back-end servers to authenticate credentials instead of just relying
on the Web server.
•Storing keys, certificates, and passwords on a Web server can be dangerous. If an attacker can
gain access to these mechanisms, the server is vulnerable to attack.
•To decrease the chances of a compromise, don’t store confidential data, such as customers’
credit card numbers, on your Web server.
•Instead, require that confidential data be entered each time users visit the Web site.
9)Unsecured communication
•Connections between the Web browser and the Web application should be encrypted to
protect information as it travels across the Internet.
•Web applications need to encrypt not only the session to the Web browser, but also sessions
to any other servers, such as back-end databases.
•This vulnerability occurs when sessions are left unencrypted. The PCI DSS requires encrypting
all credit card information sent over any network, whether it’s the Internet or a private LAN.
This vulnerability occurs when developers don’t use adequate access controls for URLs. Instead,
they rely on a “security through obscurity” model, which depends on users simply not being
aware of the location of critical files and directories. It’s like assuming that because a door isn’t
advertised as unlocked, no one will try to open it.