PROGESI: A PROxy Grammar To Enhance Web Application Firewall For SQL Injection Prevention
PROGESI: A PROxy Grammar To Enhance Web Application Firewall For SQL Injection Prevention
A web application is prone to security threats due to its open nature. The security of
these platforms is imperative for organizations of all sizes because they store
sensitive information. Consequently, exploiting web application vulnerabilities could
result in large-scale data breaches and significant brand and financial damages. SQL
injection (SQLi) represents a popular attack vector that malicious actors use to
compromise website security. Web application firewalls (WAFs) play a primary role
in preventing such malicious attack typologies. In the recent literature, several
advances have been proposed in the field of WAF enhancement to prevent SQLi
exploitation. However, many of them test the effectiveness of a WAF without
releasing a patch to fix security flaws if a WAF is bypassed. In other cases, the patch
is distributed exclusively according to the syntax specified by the WAF tested. This
paper introduces a framework that leverages PROxy Grammar to Enhance web
application firewalls for SQL Injection prevention (PROGESI). The proposed
solution can act as an intermediary layer between the targeted web server and the
incoming application level requests. Specifically, PROGESI can be used individually
or in combination with a WAF and includes a series of rules that patch SQLi
vulnerabilities exposed by a specific web server. Furthermore, it can identify and
mitigate SQLi attempts, also when attackers use mutation techniques, since the rules
used encompass generalization mechanisms. The experiments performed revealed
two strengths of PROGESI: (i) the ability to identify SQLi even in the presence of
server-side defense mechanisms, which increases as the generalization rate
implemented by the rule generation algorithm increases; (ii) impressive detection
performance even for low generalization rate values, which is higher than that
achieved by competitors using a state-of-the-art SQLi dataset.
EXISTING SYSTEM
Web application attacks have been combated by several mitigation techniques in the
current literature. Depending on the application level at which the defense line
operates, these can be divided into the following: (i) security by design solutions, i.e.,
application development that aims to limit, from the earliest stage of creation,
potential vulnerabilities; (ii) ML models developed to predict attacks on web
applications; (iii) WAF solutions for protecting web servers against malicious HTTP
traffic. In this section, a review of the methods belonging to the aforementioned
categories is presented. Then, the proposed contribution motivation that emerged
from such a revision is outlined.
Several ML-based solutions have been proposed currently to counter the detection of
SQLi attacks because of the effective outcomes achieved by such a paradigm [52]. In
[53], an artificial neural network (ANN) model is presented to distinguish between
malicious and legitimate uniform resource locators (URLs). SQLi patterns are crafted
into malicious URL, while legitimate URL consists of the most popular URL
addresses in the UK, according to a report by the Alexa service. In [54], a support
vector machine (SVM)- based classifier is used on data that include SQL tokens
extracted from the Microsoft SQL reserved keyword website. Such data were pre-
processed using an oversampling strategy to deal with class skew and the
computation of the Gini index for feature selection. In [55] and [56] a deep learning
(DL)-based model, i.e., an adaptive deep forest model, is proposed to deal with SQLi
detection, which integrates adaptive boosting and SVM as classification techniques.
A comprehensive analysis of twenty-three ML classifiers is presented in [57].
Specifically, in such an examination, classifiers are trained using injected and
legitimate SQL statements. A deep natural language model based on DL and word
sequence prediction is presented in [58].
Disadvantages
An existing system didn’t explore Implementation SQL injection (SQLi).
An existing system didn't implement Context-free grammar.
Proposed System
Advantages
SYSTEM REQUIREMENTS
Software Requirements:
Operating System - Windows XP
Coding Language - Java/J2EE(JSP,Servlet)
Front End - J2EE
Back End - MySQL