Posts

History of Nginx vulnerabilities until 2024

 CVE-2013-2028 - Buffer Overflow in Nginx This vulnerability is a buffer overflow caused by improper handling of certain chunked transfer encoding requests. It allows remote attackers to execute arbitrary code or crash the server. It was particularly dangerous as it could be exploited without authentication. CVE-2014-0133 - HTTP Header Injection in Nginx with PHP-CGI This issue allowed attackers to inject arbitrary HTTP headers by exploiting improper handling of certain HTTP request headers when Nginx is used with PHP-CGI. Attackers could manipulate headers to bypass security restrictions or conduct request-smuggling attacks. CVE-2014-3616 - SSL/TLS MITM Vulnerability (BEAST attack) This vulnerability affected configurations of Nginx with SSL/TLS. It allowed attackers to exploit weaknesses in SSL/TLS (especially SSLv3) and carry out man-in-the-middle (MITM) attacks. Although primarily an SSL issue, Nginx servers using old SSL versions were vulnerable. CVE-2015-5160 - Nginx Cache Po...

Path Traversal : Case-Sensitive Path Traversal

Summary A Case-Sensitive Path Traversal vulnerability is a security weakness where an attacker can exploit differences in case sensitivity when accessing files and directories. x Description Case-Sensitive Path Traversal Explanation On some systems (like Linux), file paths are  case-sensitive  (e.g.,  config.txt  is different from  Config.txt ). On others (like Windows), they are  case-insensitive  (treating  config.txt  and  Config.txt  as the same file). When applications don’t properly handle this difference, attackers may exploit it to: Access Restricted Files : If a file is protected by access control, using a path with a different case could sometimes bypass these protections, allowing access to sensitive information. Circumvent Filters : Some applications try to block path traversal attacks by checking the path string for malicious characters (e.g.,  ../ ). But if they do so without considering case, attackers can manipu...

Insecure Direct Object Reference (IDOR)

 Sumary Insecure Direct Object Reference (IDOR) is a vulnerability that arises when attackers can access or modify objects by manipulating identifiers used in a web application's URLs or parameters. It occurs due to missing access control checks, which fail to verify whether a user should be allowed to access specific data. Examples For instance, when a user accesses their profile, the application might generate a URL like this: https://example.org/users/123 The 123 in the URL is a direct reference to the user's record in the database, often represented by the primary key. If an attacker changes this number to 124 and gains access to another user's information, the application is vulnerable to Insecure Direct Object Reference. This happens because the app didn't properly check if the user had permission to view data for user 124 before displaying it. In some cases, the identifier may not be in the URL, but rather in the POST body, as shown in the following example: <...

Cross Origin Resource Sharing (CORS) misconfiguration

  References: Cross Origin Resource Sharing (CORS) misconfiguration https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/11-Client-side_Testing/07-Testing_Cross_Origin_Resource_Sharing#:~:text=Access%2DControl%2DAllow%2DOrigin%20is%20a%20response%20header%20used,data%20based%20on%20this%20header.

COOKIE SECURITY : Cookie without SameSite Attribute

Summary SameSite prevents the browser from sending this cookie along with cross-site requests. The main goal is to mitigate the risk of cross-origin information leakage. It also provides some protection against cross-site request forgery attacks. Possible values for the flag are none, lax, or strict. The strict value will prevent the cookie from being sent by the browser to the target site in all cross-site browsing contexts, even when following a regular link. For example, for a GitHub-like website this would mean that if a logged-in user follows a link to a private GitHub project posted on a corporate discussion forum or email, GitHub will not receive the session cookie and the user will not be able to access the project. A bank website however most likely doesn’t want to allow any transactional pages to be linked from external sites so the strict flag would be most appropriate here. The lax value provides a reasonable balance between security and usability for websites that want to ...

System Information Leak : External

 System Information Leak : External CWE-497, CWE-489, CWE-215, CWE-11, CWE-200 OWASP Top 10: PCI 3.2: 6.5.5 Improper Error Handling Summary This means that a possible debug application was found. Debug applications are tools used by developers when building web applications. They are used to test and modify web application properties, configuration information, and functions. If a debug application is left on a production server, an attacker may be able to use it to perform these tasks. Recommendations include removing the debugging interface. Explanation The severity of the exposed debug application will depend on the particular instance. At the least, it will give an attacker sensitive information about the settings and mechanics of web applications on the server. At worst, as is often the case, the debug application will allow an attacker complete control over the web application and server, as well as confidential information that either of these access. Recomendation Remove th...

Cookie Security : Cookie not Sent Over SSL

 Cookie Security : Cookie not Sent Over SSL CWE-614 OWASP Top 10: A3 PCI 3.2: 4.1 Use strong cryptography and security protocols, 6.5.4 Insecure Communications Summary This policy states that any area of the website or web application that contains sensitive information or access to privileged functionality such as remote site administration requires that all cookies are sent via SSL during an SSL session.  If a cookie is marked with the "secure" attribute, it will only be transmitted if the communications channel with the host is a secure one. Currently this means that secure cookies will only be sent to HTTPS (HTTP over SSL) servers. If secure is not specified, a cookie is considered safe to be sent in the clear over unsecured channels. Recommendation For Development: This issue will ultimately need to be rectified by your Network or Security Operations team. If necessary, implement the change in your development environment.