diff --git a/docs/misc/owasp.md b/docs/misc/owasp.md
index 23041fc..09d7686 100644
--- a/docs/misc/owasp.md
+++ b/docs/misc/owasp.md
@@ -24,8 +24,6 @@ categories: [Common Java Vulnerabilities]
 
 ## Code Injection
 
-Certainly! Below is an in-depth explanation of Code Injections in Markdown format, as requested:
-
 
 ### Code Injections
 
@@ -33,7 +31,7 @@ Code injection is a prevalent form of attack where an adversary can execute mali
 
 ### Understanding Code Injection
 
-To better understand how code injection works, it's essential to grasp the fundamental idea behind it. When a program accepts input from an external source (e.g., user input, file, network), and this input is not properly validated, it could contain malicious code or commands. If this input is then used within the program in a way that gets executed, it can lead to code injection.
+When a program accepts input from an external source (e.g., user input, file, network), and this input is not properly validated, it could contain malicious code or commands. If this input is then used within the program in a way that gets executed, it can lead to code injection.
 
 A simple illustration in Java could be using user input in a script execution scenario without proper validation. In such a case, an attacker could inject malicious code that would be executed as part of the application, leading to potentially severe security breaches.
 
@@ -85,12 +83,82 @@ Regular code reviews and security testing can help identify and fix code injecti
 By following these best practices and being mindful of the potential risks associated with user input, developers can significantly mitigate the risk of code injection vulnerabilities in their Java applications.
 
 
+---
+
+## Command Injections
+
+Command injection is a type of security vulnerability that allows an attacker to execute arbitrary commands on the host operating system. This can potentially lead to full system compromise depending on the level of privileges the application has. In Java, command injection vulnerabilities often arise when the application executes system commands with unsanitized user input.
+
+### Understanding Command Injections
+
+The crux of command injection lies in the insecure handling of user input, especially when constructing system commands. If an application takes user input and includes it in a system command without properly validating or sanitizing the input, it opens up a door for attackers to manipulate the command, injecting malicious instructions.
+
+#### Example:
+
+Consider this simplistic Java example that takes user input to construct a system command for pinging an IP address:
+
+```java
+public class CommandInjectionExample {
+    public static void main(String[] args) {
+        String userInput = args[0];
+        try {
+            Runtime.getRuntime().exec("ping " + userInput);
+        } catch (Exception e) {
+            e.printStackTrace();
+        }
+    }
+}
+```
+
+In this code snippet, the `Runtime.exec` method is used to execute a system command. The command is intended to ping an IP address, with the address being supplied by the user. However, if the user provides input like `8.8.8.8; rm -rf /`, it would result in executing a destructive command (`rm -rf /`) on the system after the ping command.
+
+### Mitigating Command Injection
+
+Preventing command injection entails adhering to secure coding practices, validating user inputs rigorously, and minimizing the use of system commands within the application.
+
+#### Input Validation and Sanitization:
+- Validate user input to ensure it conforms to expected formats.
+- Sanitize user input by removing or escaping special characters that could be used to manipulate system commands.
+
+#### Avoid System Commands:
+- Minimize the use of system commands within your application.
+- If possible, replace system command functionality with native Java code or safe libraries that provide the needed functionality.
+
+#### Use Safe APIs:
+- Utilize safe APIs that provide the needed functionality without resorting to system commands.
+
+#### Whitelisting:
+- If system commands are unavoidable, use a whitelist of allowed commands and strictly control the construction of the command string.
+- Ensure only allowed commands and parameters can be executed.
+
+#### Least Privilege Principle:
+- Run your application with the least amount of privilege necessary to perform its tasks, reducing the potential damage in case of a command injection attack.
+
+#### Logging and Monitoring:
+- Implement robust logging and monitoring to detect and respond to command injection attempts.
+
+#### Education and Code Reviews:
+- Educate developers about the risks associated with command injection and how to prevent them.
+- Perform regular code reviews and security testing to identify and fix potential command injection vulnerabilities.
+
+By adhering to these best practices, developers can significantly reduce the risk of command injection vulnerabilities in their Java applications, creating a more secure and robust application environment.
+
+Command injection is a severe security risk, and understanding how it works and how to prevent it is crucial for developing secure Java applications. This document has provided a foundational understanding of command injection, an illustrative example, and various preventative measures to mitigate this type of vulnerability.
  
+---
+
 
 
+---
 
 
 
+---
+
+
+
+---
+
 ## Injection Flaws 
 Injection flaws, particularly SQL injection, are common in Java EE applications. Injection occurs when user-supplied data is sent to an interpreter as part of a command or query. The attacker’s hostile data tricks the interpreter into  executing unintended commands or changing data.