The essence of command injection attacks in web applications

By Zhendong Su, Gary Wassermann. ACM-SIGACT Symposium on Principles of Programming Languages, 2006

664 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Information Systems, Software

View Paper: https://www.semanticscholar.org/paper/088a382a5af6a44ccb69c2f49517bf8d99ab6759

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 Software

Citations in the corpus

Automatic creation of SQL Injection and cross-site scripting attacks (2009, background): “The essence of an SQLI attack is a change in the structure of the SQL statement that preserves its syntactic validity (otherwise, the database rejects the statement and the attack attempt is unsuccessful) [27].”
Raksha: a flexible information flow architecture for software security (2007, methodology): “Our current SQL validation routine is also not as advanced as the algorithm in [23], since we scan for tainted command characters without parsing the SQL grammar.”
Taint-Enhanced Policy Enforcement: A Practical Approach to Defeat a Wide Range of Attacks (2006, methodology): “As discussed in Section 7, Su et al [27] describe a technique for detecting SQL injection attacks using syntax analysis.”
A Classification of SQL Injection Attacks and Countermeasures (2006, background): “Interested readers can refer to [35] for a more formal definition of SQLIAs.”
The Instruction Hierarchy: Training LLMs to Prioritize Privileged Instructions (2024, background): “…operating systems use a hierarchy of access and control (Corbat´o & Vyssotsky, 1965; Ritchie & Thompson, 1974) and attacks such as SQL injections (Su & Wassermann, 2006) and command injections (Zhong et al., 2024) are solved by not treating user inputs as privileged instructions (Thomas et al.,…”
Defeating script injection attacks with browser-enforced embedded policies (2007, background): “cult, however, and attacks such as the Samy and Yamanner worms have exploited .ltering weaknesses.”
Merlin: specification inference for explicit information flow problems (2009, background): “The growing importance of explicit information flow is evidences by the abundance of analysis tools for information flow tracking and violation detection at the level of the language, runtime, operating system, and hardware [2, 3, 7, 9–12, 16, 18, 19, 22, 27, 29, 33, 36].”
Saner: Composing Static and Dynamic Analysis to Validate Sanitization in Web Applications (2008, background): “These vulnerability detectors are typically based on some form of data flow analysis that tracks the flow of information from the application’s inputs (called sources) to points in the program that represent security-relevant operations (called sinks).”
Automated program repair (2019, background): “For example, such repair techniques can enforce control flow integrity [30], prevent code injections [31], automatically insert sanitizers of untrusted input, or enforce automatically inferred safety properties [32].”
StruQ: Defending Against Prompt Injection with Structured Queries (2024, neutral): “SQL injection arises because the API to the database accepts a single string containing a SQL query, thereby mixing control (the type of SQL command to be performed, e.g., SELECT ) with data (e.g., a keyword to match on) [34, 35, 32].”
CICIoT2023: A Real-Time Dataset and Benchmark for Large-Scale Attacks in IoT Environment (2023, background): “The goal of an SQL injection attack is to gain unauthorized access to a database, steal sensitive information, or execute arbitrary commands on the database server [79]; • Command Injection: an attack that targets web applications by injecting malicious commands into an input field with the ultimate”