Introduction To Server Side Attack: Server Side Request Forgery (SSRF)

Welcome folks, today we will learn about a famous server-side attack, known as server-side request forgery (SSRF). In today's digital era, having a strong grasp of application security is crucial, given the complex threats that can endanger both personal and organisational data. One such threat is Server-Side Request Forgery (SSRF). This article will help you explain SSRF in an easy-to-understand manner, highlight real-world examples, provide practical advice on how to defend against such vulnerabilities, and delve into attacks which SSRF enables.

What is SSRF and how it works

It refers to a security issue where an attacker deceives a web application or API into initiating requests towards internal services. This can result in unauthorised access, exposure of sensitive data, compromise of systems, and execution of malicious code. Attackers manipulate inadequate input checks to direct applications to undesirable internet destinations, bypassing protections like firewalls or VPNs.

Working Of SSRF Attack

In an SSRF attack, the attacker manipulates the server into making HTTP requests to internal systems or external servers. They create a specially crafted URL which the server accesses, then sends the results back to the attacker.This exposes sensitive information or grants the attacker access to these resources. Due to the server's inherent trust in client requests, the attacker can circumvent security protocols and access restricted areas.

Example of a Vulnerable Python Code Snippet for SSRF

The Python code snippet mentioned is designed to fetch and return the content of a URL specified by the user. The vulnerability in this code is explained as follows:

1. Line with url = request.args["url"]: Directly takes a user-provided URL without validation, allowing for malicious URLs that could target internal services.
2. Line with urllib.request.urlopen(url).read(): Executes the URL request, which could unintentionally access restricted external or internal resources.

Types of risks Enabled by SSRF

SSRF can open the door to a whole lot of attacks, depending on the character of the application and the environment:

- Bypassing Firewalls: SSRF provides a pathway for attackers to bypass/circumvent firewall security, granting them unauthorised access to protected areas of an organisation's internal network. Like an intruder utilising a valid access card, the fraudulent request is perceived as trustworthy, compelling the internal mechanisms to comply without restrictions.

- Data Breach Risks: SSRF enables attackers to infiltrate restricted internal networks, accessing highly confidential information. They are capable of querying internal databases or APIs to extract critical data, including personal details of employees and proprietary business information. This form of attack is particularly covert and potentially leads to considerable breaches in data security.

- Internal Network Mapping: By leveraging SSRF, assailants can conduct reconnaissance within a company’s network infrastructure. They achieve this by initiating requests to different internal IP addresses, which helps them chart out active services, discover open ports, and identify security weaknesses that could be exploited in subsequent attacks.

- Executing Remote Code: In extreme scenarios, SSRF vulnerabilities might escalate to remote code execution, allowing attackers to run malicious code on the server. This could occur if the server is deceived into fetching and running a script from what seems to be a reliable source.

- Service Disruption: SSRF is also a tool for initiating denial of service (DoS) attacks on internal systems ill-equipped for external pressures or high request volumes. Such attacks can cripple system functionalities, causing significant delays and operational disruptions.

Types of SSRF

- Basic SSRF: In the basic SSRF, an attacker injects a malicious URL as part of the user input, making the server send a request to the targeted resource. This allows the attacker to directly view the server's response and collect details about the internal network, like methods to extract data or pinpoint available services.

- Blind SSRF: Blind SSRF vulnerabilities occur when an application is manipulated to send an HTTP request to a user-specified URL on the backend, yet the application does not include the backends’ response in its own frontend output. The impact of blind SSRF vulnerabilities tends to be less severe than that of fully observable SSRF vulnerabilities due to their one-way interaction. They generally do not allow for straightforward exploitation to extract sensitive information from back-end systems. However, under certain circumstances, they can still be manipulated to enable complete remote code execution.

- Semi-Blind SSRF: This type is more Like a blind SSRF, this form of attack typically yields limited data. However, the information it does provide, such as error messages or response times, can be valuable for attackers, aiding them in crafting more sophisticated attacks later on.

Implications of SSRF via CVE-2023-24329 in Python

A URL parsing or SSRF vulnerability in the Python programming language before 3.11.4 was announced on February 17, 2023, and assigned the ID CVE-2023–24329. The urllib.parse module, which has functions for disassembling URLs into their component parts and reassembling them into whole URLs, is the source of the problem.

Vulnerable Code Snippet:

Coming to the vulnerability, here is the screenshot of the vulnerable code snippet attached below. The code snippet allows blocking certain urls based on their scheme and host.

Exploitation:

To replicate the given vulnerability, we would be using the following git repo by H4R335HR.

As per given screenshot, when entering the following payload with extra space: https://youtube.com. The check is bypassed. This vulnerability has affected millions of python repositories which simply allowed an extra space to be neglected when entering the user-controlled input.

Remediation:

Given the severity of CVE-2023-24329, it is strongly advised that Python be updated to the most recent version as soon as feasible. The fix was released in the following versions:

- Python 3.12 (and above) - Python 3.11.4 - Python 3.10.12 - Python 3.9.17 - Python 3.8.17 - Python 3.7.17

Therefore, patching Python to one of these releases will fix the security flaw and stop its exploitation.

For example:

If updating the Python runtime is not practicable, the vulnerability report suggests using string.lstrip() as a workaround:

Python Code Example for Preventing SSRF Attacks

To effectively counter SSRF threats, organisations need to adopt a vigilant security stance with proactive measures. Here are some key strategies to enhance your systems' defence against SSRF attacks:

- 1. Validate Inputs: Ensure thorough validation of URLs and other inputs to confirm they are free from malicious links. - 2. Restrict Server Requests: Control your server's capabilities to prevent unnecessary HTTP requests to unfamiliar destinations. - 3. Employ Network Segmentation: Implement network segmentation to contain and limit the scope of potential SSRF exploits across your network.

Here is a straightforward Python example demonstrating how to mitigate SSRF by validating URLs against a predefined whitelist.

The code snippet prevents SSRF attacks through the following mechanisms:

- Domain Whitelist: Utilises a predefined list (DOMAINS_WHITELIST) containing trusted domains such as 'domain1.com' and 'domain2.com'. - URL Validation: Parses the user-provided URL to extract its hostname using urllib.parse.urlparse(url). - Conditional Access: Executes the HTTP request using urllib.request.urlopen(url).read() only if the parsed hostname is in the DOMAINS_WHITELIST, thereby blocking requests to unauthorised domains.

Conclusion

In conclusion, tackling Server-Side Request Forgery (SSRF) vulnerabilities is key to keeping web applications safe. SSRF can be tricky as it allows attackers to trick a server into performing actions without permission. To guard against such threats, strong input validation, using allowlists, and correctly setting up server request handlers are crucial. By staying informed and applying these proactive security measures, developers and administrators can protect their systems from the serious risks associated with SSRF attacks. Let's continue to evolve and strengthen our defences as we navigate the complex landscape of cybersecurity.