In this blog

In this fourth installment of our 5 part series on OWASP's API Top Ten, we delve into categories 7 and 8 with Server Side Request Forgery and Security Misconfiguration. As modern applications and the network become more abstracted, Security Misconfiguration is a consistent problem due to the complexity and interconnected nation of APIs and applications. With that, let's dive right in.

In the realm of API security, one of the critical vulnerabilities to be aware of is Server Side Request Forgery (SSRF). SSRF occurs when an attacker can manipulate the server-side requests made by an API to access or interact with resources that should be restricted. This blog post will explore what SSRF is, why it poses a significant risk to API security, and how organizations can mitigate this vulnerability.

Understanding Server Side Request Forgery (SSRF)

SSRF is a type of security vulnerability that allows an attacker to make unauthorized requests from the server side of an API. By manipulating the API's requests, an attacker can potentially access internal resources that are not intended to be exposed, such as local files, databases or other APIs. SSRF often occurs when an API does not properly validate or restrict the URLs or endpoints it can access.

Forger Arrested

Risks associated with SSRF

SSRF poses several risks to the security and integrity of an API. By exploiting SSRF, an attacker can bypass network security measures and access sensitive information or resources. For example, an attacker could make requests to internal APIs or services and retrieve confidential data, modify data or even perform actions that could lead to a complete compromise of the system. Additionally, SSRF can be leveraged to perform attacks such as port scanning, remote code execution, or accessing internal network resources.

In-App and API security, another critical vulnerability organizations should be aware of is Security Misconfiguration. Security Misconfiguration occurs when an App, API, or underlying technology is not configured correctly, leaving it vulnerable to various attacks and exploitation. Let's explore what Security Misconfiguration is and the risks associated with it.

Understanding Security Misconfiguration

Security Misconfiguration refers to the incorrect configuration of security settings and controls in an API. It can occur at various levels, including server configurations, framework settings, database configurations and API endpoints. When security measures are not adequately implemented or are left in their default and insecure states, it opens up avenues for potential attacks.

Security Misconfiguration

Risks associated with Security Misconfiguration

Security Misconfiguration can have severe consequences for both the API and the organization. By leaving security settings in an insecure state, attackers may exploit these vulnerabilities to gain unauthorized access, steal sensitive data, modify or delete data or even compromise the entire system. Additionally, Security Misconfiguration can lead to data breaches, unauthorized access to backend systems and reputational damage for the organization.

Common examples of Security Misconfiguration include leaving default passwords unchanged, exposing sensitive error messages, having unnecessary enabled features and not properly restricting access to sensitive API endpoints. These misconfigurations allow attackers to exploit and compromise the API's security.


Server Side Request Forgery (SSRF) is a significant threat to Apps and APIs, allowing attackers to manipulate server-side requests and access sensitive resources. Understanding the risks associated with SSRF and implementing appropriate security measures can help organizations protect their APIs and the data they handle. By validating input, implementing network segmentation, restricting access to external resources, keeping dependencies updated, and conducting ongoing security testing, organizations can reduce the likelihood of SSRF attacks and safeguard their API infrastructure.

Security Misconfiguration is another significant and insidious vulnerability that can expose APIs to various security risks and compromise data confidentiality, integrity and availability. Understanding the risks associated with Security Misconfiguration and implementing appropriate security measures is crucial for organizations to protect their APIs from potential attacks. By following best practices such as changing default configurations, regular patching, implementing the principle of least privilege, secure error handling, conducting security audits, and deploying securely, organizations can enhance the security posture of their APIs and mitigate the risk of Security Misconfiguration.

Security is an ongoing process, and regular assessments, updates and monitoring are essential to ensure the continued protection of APIs against evolving threats.