Securing web application code by static analysis and runtime protection

By Yao-Wen Huang, Fang Yu, Christian Hang, Chung-Hung Tsai, Der-Tsai Lee, S. Kuo. The Web Conference, 2004

678 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Information Systems, Signal Processing

View Paper: https://www.semanticscholar.org/paper/6c76aeeea6052544522caa157cc16b700b977534

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Artificial Intelligence

In Information Systems

In Signal Processing

Citations in the corpus

Taint-Enhanced Policy Enforcement: A Practical Approach to Defeat a Wide Range of Attacks (2006, background): “Static taint analysis techniques have been proposed by many for finding security vulnerabilities, including input validation errors in web applications [17, 14, 32], user/kernel pointer bugs [15], format string bugs [26], and bugs in placement of authorization hooks [34].”
Sound and precise analysis of web applications for injection vulnerabilities (2007, background): “were perhaps the first to apply it to SQLCIVs [11].”
DynaMine: finding common error patterns by mining software revision histories (2005, background): “A great deal of attention has lately been given to addressing application-specific software bugs such as errors in operating system drivers [4, 13], security errors [20, 32], or errors in reliabilitycritical embedded software in domains like avionics [7, 8].”
The essence of command injection attacks in web applications (2006, methodology): “In pa rticular, there are two recent techniques using static analysis to tra ck he flow of untrusted input through a program: one based on a type system [15] (similar to CQual [10]) and one based on a pointsto analysis [24] (using a precise points-to analysis for Jav a [43] and policies specified in”
Pixy: a static analysis tool for detecting Web application vulnerabilities (2006, methodology): “Dynamic tools (e.g., [9] [18] [21], and Perl's taint mode try to detect attacks while executing the audited program, whereas static analyzers ([10] [11] [15] [16]) scan the Web application's source code for vulnerabilities.”
State of the Art: Automated Black-Box Web Application Vulnerability Testing (2010, background): “Work by Wassermann [20], Lam [21], Kie˙ [22], Jovanovic [23], and Huang [ 24 ] all fall into this category.”
Edge Computing Security: State of the Art and Challenges (2019, background): “[111], which not only achieves defense against SQL injection on a full surface but also manages to run in real time.”
Static detection of cross-site scripting vulnerabilities (2008, methodology): “presented one of the first taint analyses for web applications and applied it to SQL injection [11].”
Finding Security Vulnerabilities in Java Applications with Static Analysis (2005, methodology): “The WebSSARI project uses combined unsound static and dynamic analysis in the context of analyzing PHP programs [23].”
Saner: Composing Static and Dynamic Analysis to Validate Sanitization in Web Applications (2008, background): “For example, an application might check that the number of items to purchase, sent as part of a form submission, is actually provided as an integer value and not as a nonnumeric string or a float.”
Automatic creation of SQL Injection and cross-site scripting attacks (2009, background): “Static and dynamic approaches can be combined [14,15].”
Noxes: a client-side solution for mitigating cross-site scripting attacks (2006, background): “Similarly, in their follow-up work [19], Huang et al.”
A Classification of SQL Injection Attacks and Countermeasures (2006, methodology): “In fact, many of the SQL injection vulnerabilities discovered in real applications are due to human errors: developers forgot to add checks or did not perform adequate input validation [20, 23, 33].”