Elvis Wiki - User contributions [en]

OWASP Zed Attack Proxy

2024-01-07T04:16:25Z

HVergara: /* Features */

[[File:OWASP ZAP.png|thumb| OWASP ZAP https://www.zaproxy.org/ <ref name="OWASP ZAP"/>]]

OWASP Zed Attack Proxy (ZAP)<ref name="getting-started"/> is a comprehensive, open-source penetration
testing tool developed by The Software Security Project (SSP)<ref name="Software Security"/> under
OWASP. Specifically designed for assessing web application security, it functions as
a “Manipulator-in-the-middle proxy<ref name="Manipulator-in-the-middle proxy"/>, intercepting and modifying messages
between the tester’s browser and the application.
ZAP is versatile and user-friendly, catering to both security novices and specialists.
It is compatible with major operating systems and Docker, offering both manual and
automated testing capabilities to identify and report vulnerabilities in web applications.
The tool features a detailed desktop UI, a powerful API, command-line functionality,
and is extensible through various add-ons available in the ZAP Marketplace.
Emphasizing responsible use, ZAP simulates real attacks, underscoring the importance
of using it only on applications for which the user has testing permission. Its
multifunctionality, adaptability, and focus on responsible usage make ZAP a valuable
asset in enhancing web application security.

The Open Web Application Security Project(OWASP) is a non-profit organization
aimed at improving the security of applications and services on the internet. Another
important tool provided by OWASP is the ”OWASP Top 10” list. This list summarizes
the ten most common security risks for web applications and is regularly updated based
on data and trends in web application security. Based on the ”OWASP Top Ten,”
various tools are developed to enhance security in the digital world, and one of these
is OWASP ZAP.

===Features===
OWASP ZAP is a comprehensive tool in web application security, equipped with various modules to detect and analyze a wide range of vulnerabilities. With features like multiple attack modes and structured scanning, it plays a crucial role in identifying and mitigating potential threats in web applications.

'''Security Scanner for Web Applications:'''
OWASP ZAP is utilized as a security scanner specifically designed for web applications.
Various Modules:<ref name="ZAPPROXY. Features."/>

'''It is equipped with various modules including:'''
* '''Proxy:''' For capturing data
* '''Fuzzer:''' For identifying vulnerabilities
* '''Spider:''' For discovering web applications
* '''Scanner:''' For conducting active and passive attacks
* '''Dictionary Method:''' To access files

'''Vulnerability Detection:'''
OWASP ZAP is capable of detecting medium and low-level risks and vulnerabilities such as<ref name="OWASP. Attacks."/>:
* '''URL rewriting'''
* '''Application error disclosure'''
* '''X Frame Options (XFO) header not set'''
* '''SQL injection'''
* '''Cross-Site Request Forgery (CSRF)'''
* '''Cookie without secure flag and HTTP only'''

'''Scanning Process:'''
The scanning process in ZAP includes giving the Host Name/Host ID as input,
carrying out the scanning to identify flaws, discovering vulnerabilities, performing risk
analysis, and concluding the results.
Modes of Attack:
ZAP offers four modes of attack: standard mode, protected mode, attack mode,
and safe mode. These modes are used to identify vulnerabilities on the web.
Risk Analysis:
After identifying vulnerabilities, the process of risk analysis is performed, categorizing
risks into low, high, informational, and medium.

==Methodology==
There are various ways to analyze risks in OWASP. This is based on standard methods and is tailored to personalized security applications<ref name="Penetration testing methodologies"/>.
* '''Step 1: Pre-engagement Interactions:''' This phase involves establishing clear goals, scope, and legal boundaries for the security assessment or penetration test, often through contractual agreements.
* '''Step 2: Intelligence Gathering:''' The focus here is on collecting as much information as possible about the target system or organization, which could include public data or internal details.
* '''Step 3: Threat Modeling:''' In this optional step, potential threats and attack vectors are identified and assessed, helping to prioritize the focus areas for the assessment.
* '''Step 4: Vulnerability Analysis:''' This critical phase involves identifying and analyzing vulnerabilities within the system, which could be prone to exploitation.
* '''Step 5: Exploitation:''' This step involves attempting to exploit the identified vulnerabilities, demonstrating the potential impact of a breach.
* '''Step 6: Post Exploitation:''' After successful exploitation, this phase includes actions like collecting sensitive data, maintaining access, and understanding the extent of the compromise.
* '''Step 7: Reporting:''' A comprehensive report is prepared, detailing vulnerabilities, the methods used to exploit them, and the potential impact, providing valuable insights for mitigation.
* '''Step 8: Resolution and Re-Testing:''' Finally, the focus shifts to resolving the identified vulnerabilities and then re-testing to ensure that the fixes are effective and the vulnerabilities are fully addressed.

==Execution==
In this phase, we apply our findings in a practical manner. We conduct controlled attacks
on identified vulnerabilities, such as exploiting the HTTP security flaw, within a
safe testing environment. This allows us to observe the system’s response without disrupting
normal operations. Every step is documented to develop effective improvement
strategies.

===Pre-engagement Interactions:===
In this phase, we define our target, which in this case is our web application at http://192.168.0.5 We plan to conduct an automatic scan to identify potential vulnerabilities. Normally, during this phase, we would also set a specific time for the scan or attack. This allows us to create an official document confirming that both teams agree to conduct the vulnerability scan. However, since this is merely a test environment of our own web application, adhering to the official process is not necessary in this instance

===Intelligence Gathering:===
Our target is http://192.168.0.5, an internal DNS server. This server plays a key role in our network as it is responsible for mapping domain names to IP addresses. Our task in the intelligence gathering phase includes collecting details about the server configuration and identifying potential vulnerabilities to pinpoint possible security risks.

===Threat Modeling(Option):===
In this step, we conduct a scan focused exclusively on HTTP vulnerabilities. The main issue here is that the connection via HTTP is unencrypted, which means that all traffic, including sensitive information such as login credentials and passwords, can potentially be intercepted and read. This vulnerability makes the system particularly susceptible to Man-in-the-Middle attacks.

[[File:Threat_Modeling(option)_-_A.jpg|400px]]

Figure 1: OWASP ZAP Automated Scan

[[File:Threat_Modeling(option)_-_B.jpg|400px]]

Figure 2: Vulnerability Scan Results

===Vulnerability Analysis:===
In this step, we analyze the data and vulnerabilities identified during our automated scan. As mentioned in the Threat Modeling phase, our focus is on HTTP vulnerabilities. We assess the severity and potential impacts of these security flaws to develop appropriate countermeasures.

===Exploitation:===
In this step, we demonstrate an exploitation using login data. We employ Wireshark to monitor the data traffic between the user and the web application. In this scenario, Wireshark acts as a Man-in-the-Middle tool, enabling us to analyze the transmitted packets and uncover vulnerabilities in the data transmission.

[[File:Explotation_-_A.jpg|400px]]

Figure 3: Objective for Password Sniffing

[[File:Explotation_-_B.jpg|800px]]

Figure 4: Wireshark Packet Capture for Password Sniffing

===Post Exploitation:===
In this step, we investigate what information can be accessed after an attack, especially when unencrypted packets have been transmitted.

[[File:Post_Explotation_-_A.jpg|600px]]

Figure 5: Wireshark Packet Analysis for Login Password

===Reporting:===
In this step, we will create a report to compare the state before and after addressing the vulnerability. OWASP ZAP also offers the capability to generate such a report.

[[File:Reporting_-_A.jpg|400px]]

Figure 6: Vulnerability Report in OWASP ZAP

[[File:Reporting_-_C.jpg|600px]]

Figure 7: OWASP ZAP Report

===Resolution and Re-Testing:===
In this step, we propose various methods to eliminate the identified vulnerability. When focusing on our specific example, it is important to consider two key configurations that need to be addressed:

*'''Encrypted Connection (HTTPS):''' To set up an encrypted connection, it is necessary to create an SSL/TLS certificate with a FQDN (Fully Qualified Domain Name) for the web application. This ensures that data transmission is secure and the server only responds to encrypted requests directed to this specific domain name.

[[File:Resolution_and_re-testing_-_HTTPS_A.jpg|600px]]

Figure 8: Automated scan with encrypted connection

*'''Web Application IP:''' It is also important to ensure that the web application does not respond to HTTP requests directed specifically to its IP address. This serves as an additional security measure by preventing the application from being accessible via unencrypted HTTP connections.

[[File:Resolution_and_re-testing_-_Web_Applucation_IP_A.jpg|400px]]

Figure 9: Modify a Linux File to Prevent HTTP Responses to a Specific IP Address

[[File:Resolution_and_re-testing_-_Web_Applucation_IP_C.jpg|800px]]

Figure 10: Results of Automated Scan After Encrypted Connection

==Conclusion==
OWASP ZAP represents a comprehensive open-source software that can be used to identify various security vulnerabilities in web applications. It is characterized by a multitude of directly applicable functions that enable effective use. However, it is advisable to use this tool with care. When properly applied, OWASP ZAP can contribute to the detection and remediation of security risks in both active and in-development web applications.

== References ==
<references>
<ref name="OWASP ZAP">https://www.zaproxy.org/</ref>
<ref name="getting-started">OWASP. https://www.zaproxy.org/getting-started/, 2023. access 09.12.2023.</ref>
<ref name="Software Security">Software Security Project. Welcoming zap to the software security project. https://softwaresecurityproject.org/blog/welcoming-zap-to-the-software-security-project/, 2023. access 09.12.2023.</ref>
<ref name="Manipulator-in-the-middle proxy">OWASP. Manipulator-in-the-middle proxy. https://www.zaproxy.org/docs/desktop/start/features/intercept/, 2023. access 09.12.2023.</ref>
<ref name="ZAPPROXY. Features.">ZAPPROXY. Features. https://www.zaproxy.org/docs/desktop/start/features/, ZAPPROXY. access 09.12.2023.</ref>
<ref name="OWASP. Attacks.">OWASP. Attacks. https://owasp.org/www-community/attacks/, 2023. access 09.12.2023.</ref>
<ref name="Penetration testing methodologies">OWASP. Penetration testing methodologies. https://owasp.org/www-project-web-security-testing-guide/latest/3-The_OWASP_Testing_Framework/1-Penetration_Testing_Methodologies#penetration-testing-execution-standard, 2023. access 09.12.2023.</ref>

</references>

[[Category:Pentesting]]

OWASP Zed Attack Proxy

2024-01-07T04:14:22Z

HVergara: /* Resolution and Re-Testing: */

[[File:OWASP ZAP.png|thumb| OWASP ZAP https://www.zaproxy.org/ <ref name="OWASP ZAP"/>]]

OWASP Zed Attack Proxy (ZAP)<ref name="getting-started"/> is a comprehensive, open-source penetration
testing tool developed by The Software Security Project (SSP)<ref name="Software Security"/> under
OWASP. Specifically designed for assessing web application security, it functions as
a “Manipulator-in-the-middle proxy<ref name="Manipulator-in-the-middle proxy"/>, intercepting and modifying messages
between the tester’s browser and the application.
ZAP is versatile and user-friendly, catering to both security novices and specialists.
It is compatible with major operating systems and Docker, offering both manual and
automated testing capabilities to identify and report vulnerabilities in web applications.
The tool features a detailed desktop UI, a powerful API, command-line functionality,
and is extensible through various add-ons available in the ZAP Marketplace.
Emphasizing responsible use, ZAP simulates real attacks, underscoring the importance
of using it only on applications for which the user has testing permission. Its
multifunctionality, adaptability, and focus on responsible usage make ZAP a valuable
asset in enhancing web application security.

The Open Web Application Security Project(OWASP) is a non-profit organization
aimed at improving the security of applications and services on the internet. Another
important tool provided by OWASP is the ”OWASP Top 10” list. This list summarizes
the ten most common security risks for web applications and is regularly updated based
on data and trends in web application security. Based on the ”OWASP Top Ten,”
various tools are developed to enhance security in the digital world, and one of these
is OWASP ZAP.

===Features===
OWASP ZAP is a comprehensive tool in web application security, equipped with various modules to detect and analyze a wide range of vulnerabilities. With features like multiple attack modes and structured scanning, it plays a crucial role in identifying and mitigating potential threats in web applications.

Security Scanner for Web Applications:
OWASP ZAP is utilized as a security scanner specifically designed for web applications.
Various Modules:<ref name="ZAPPROXY. Features."/>

It is equipped with various modules including:
* '''Proxy:''' For capturing data
* '''Fuzzer:''' For identifying vulnerabilities
* '''Spider:''' For discovering web applications
* '''Scanner:''' For conducting active and passive attacks
* '''Dictionary Method:''' To access files

Vulnerability Detection:
OWASP ZAP is capable of detecting medium and low-level risks and vulnerabilities such as<ref name="OWASP. Attacks."/>:
* '''URL rewriting'''
* '''Application error disclosure'''
* '''X Frame Options (XFO) header not set'''
* '''SQL injection'''
* '''Cross-Site Request Forgery (CSRF)'''
* '''Cookie without secure flag and HTTP only'''

'''Scanning Process:'''
The scanning process in ZAP includes giving the Host Name/Host ID as input,
carrying out the scanning to identify flaws, discovering vulnerabilities, performing risk
analysis, and concluding the results.
Modes of Attack:
ZAP offers four modes of attack: standard mode, protected mode, attack mode,
and safe mode. These modes are used to identify vulnerabilities on the web.
Risk Analysis:
After identifying vulnerabilities, the process of risk analysis is performed, categorizing
risks into low, high, informational, and medium.

==Methodology==
There are various ways to analyze risks in OWASP. This is based on standard methods and is tailored to personalized security applications<ref name="Penetration testing methodologies"/>.
* '''Step 1: Pre-engagement Interactions:''' This phase involves establishing clear goals, scope, and legal boundaries for the security assessment or penetration test, often through contractual agreements.
* '''Step 2: Intelligence Gathering:''' The focus here is on collecting as much information as possible about the target system or organization, which could include public data or internal details.
* '''Step 3: Threat Modeling:''' In this optional step, potential threats and attack vectors are identified and assessed, helping to prioritize the focus areas for the assessment.
* '''Step 4: Vulnerability Analysis:''' This critical phase involves identifying and analyzing vulnerabilities within the system, which could be prone to exploitation.
* '''Step 5: Exploitation:''' This step involves attempting to exploit the identified vulnerabilities, demonstrating the potential impact of a breach.
* '''Step 6: Post Exploitation:''' After successful exploitation, this phase includes actions like collecting sensitive data, maintaining access, and understanding the extent of the compromise.
* '''Step 7: Reporting:''' A comprehensive report is prepared, detailing vulnerabilities, the methods used to exploit them, and the potential impact, providing valuable insights for mitigation.
* '''Step 8: Resolution and Re-Testing:''' Finally, the focus shifts to resolving the identified vulnerabilities and then re-testing to ensure that the fixes are effective and the vulnerabilities are fully addressed.

==Execution==
In this phase, we apply our findings in a practical manner. We conduct controlled attacks
on identified vulnerabilities, such as exploiting the HTTP security flaw, within a
safe testing environment. This allows us to observe the system’s response without disrupting
normal operations. Every step is documented to develop effective improvement
strategies.

===Pre-engagement Interactions:===
In this phase, we define our target, which in this case is our web application at http://192.168.0.5 We plan to conduct an automatic scan to identify potential vulnerabilities. Normally, during this phase, we would also set a specific time for the scan or attack. This allows us to create an official document confirming that both teams agree to conduct the vulnerability scan. However, since this is merely a test environment of our own web application, adhering to the official process is not necessary in this instance

===Intelligence Gathering:===
Our target is http://192.168.0.5, an internal DNS server. This server plays a key role in our network as it is responsible for mapping domain names to IP addresses. Our task in the intelligence gathering phase includes collecting details about the server configuration and identifying potential vulnerabilities to pinpoint possible security risks.

===Threat Modeling(Option):===
In this step, we conduct a scan focused exclusively on HTTP vulnerabilities. The main issue here is that the connection via HTTP is unencrypted, which means that all traffic, including sensitive information such as login credentials and passwords, can potentially be intercepted and read. This vulnerability makes the system particularly susceptible to Man-in-the-Middle attacks.

[[File:Threat_Modeling(option)_-_A.jpg|400px]]

Figure 1: OWASP ZAP Automated Scan

[[File:Threat_Modeling(option)_-_B.jpg|400px]]

Figure 2: Vulnerability Scan Results

===Vulnerability Analysis:===
In this step, we analyze the data and vulnerabilities identified during our automated scan. As mentioned in the Threat Modeling phase, our focus is on HTTP vulnerabilities. We assess the severity and potential impacts of these security flaws to develop appropriate countermeasures.

===Exploitation:===
In this step, we demonstrate an exploitation using login data. We employ Wireshark to monitor the data traffic between the user and the web application. In this scenario, Wireshark acts as a Man-in-the-Middle tool, enabling us to analyze the transmitted packets and uncover vulnerabilities in the data transmission.

[[File:Explotation_-_A.jpg|400px]]

Figure 3: Objective for Password Sniffing

[[File:Explotation_-_B.jpg|800px]]

Figure 4: Wireshark Packet Capture for Password Sniffing

===Post Exploitation:===
In this step, we investigate what information can be accessed after an attack, especially when unencrypted packets have been transmitted.

[[File:Post_Explotation_-_A.jpg|600px]]

Figure 5: Wireshark Packet Analysis for Login Password

===Reporting:===
In this step, we will create a report to compare the state before and after addressing the vulnerability. OWASP ZAP also offers the capability to generate such a report.

[[File:Reporting_-_A.jpg|400px]]

Figure 6: Vulnerability Report in OWASP ZAP

[[File:Reporting_-_C.jpg|600px]]

Figure 7: OWASP ZAP Report

===Resolution and Re-Testing:===
In this step, we propose various methods to eliminate the identified vulnerability. When focusing on our specific example, it is important to consider two key configurations that need to be addressed:

*'''Encrypted Connection (HTTPS):''' To set up an encrypted connection, it is necessary to create an SSL/TLS certificate with a FQDN (Fully Qualified Domain Name) for the web application. This ensures that data transmission is secure and the server only responds to encrypted requests directed to this specific domain name.

[[File:Resolution_and_re-testing_-_HTTPS_A.jpg|600px]]

Figure 8: Automated scan with encrypted connection

*'''Web Application IP:''' It is also important to ensure that the web application does not respond to HTTP requests directed specifically to its IP address. This serves as an additional security measure by preventing the application from being accessible via unencrypted HTTP connections.

[[File:Resolution_and_re-testing_-_Web_Applucation_IP_A.jpg|400px]]

Figure 9: Modify a Linux File to Prevent HTTP Responses to a Specific IP Address

[[File:Resolution_and_re-testing_-_Web_Applucation_IP_C.jpg|800px]]

Figure 10: Results of Automated Scan After Encrypted Connection

==Conclusion==
OWASP ZAP represents a comprehensive open-source software that can be used to identify various security vulnerabilities in web applications. It is characterized by a multitude of directly applicable functions that enable effective use. However, it is advisable to use this tool with care. When properly applied, OWASP ZAP can contribute to the detection and remediation of security risks in both active and in-development web applications.

== References ==
<references>
<ref name="OWASP ZAP">https://www.zaproxy.org/</ref>
<ref name="getting-started">OWASP. https://www.zaproxy.org/getting-started/, 2023. access 09.12.2023.</ref>
<ref name="Software Security">Software Security Project. Welcoming zap to the software security project. https://softwaresecurityproject.org/blog/welcoming-zap-to-the-software-security-project/, 2023. access 09.12.2023.</ref>
<ref name="Manipulator-in-the-middle proxy">OWASP. Manipulator-in-the-middle proxy. https://www.zaproxy.org/docs/desktop/start/features/intercept/, 2023. access 09.12.2023.</ref>
<ref name="ZAPPROXY. Features.">ZAPPROXY. Features. https://www.zaproxy.org/docs/desktop/start/features/, ZAPPROXY. access 09.12.2023.</ref>
<ref name="OWASP. Attacks.">OWASP. Attacks. https://owasp.org/www-community/attacks/, 2023. access 09.12.2023.</ref>
<ref name="Penetration testing methodologies">OWASP. Penetration testing methodologies. https://owasp.org/www-project-web-security-testing-guide/latest/3-The_OWASP_Testing_Framework/1-Penetration_Testing_Methodologies#penetration-testing-execution-standard, 2023. access 09.12.2023.</ref>

</references>

[[Category:Pentesting]]

2024-01-07T03:12:49Z

HVergara:

File:Threat Modeling(option) - A.jpg

2024-01-07T03:12:19Z

HVergara: