Posts

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. 

COOKIE SECURITY : Persistent Cookie

  COOKIE SECURITY : Persistent Cookie CWE-613, CWE-539 OWASP Top 10: A3 PCI 3.2: 6.5.1 Injection Flaws, 6.5.3 Insecure Cryptographic Storage Summary Cookies are small bits of data that are sent by the web application but stored locally in the browser. This lets the application use the cookie to pass information between pages and store variable information. The web application controls what information is stored in a cookie and how it is used. Typical types of information stored in cookies are session Identifiers, personalization and customization information, and in rare cases even usernames to enable automated logins. There are two different types of cookies: session cookies and persistent cookies. Session cookies only live in the browser's memory, and are not stored anywhere. Persistent cookies, however, are stored on the browser's hard drive. This can cause security and privacy issues depending on the information stored in the cookie and how it is accessed. Explanation Persi...

Insecure Transport - Weak SSL Cipher

Weak SSL Cipher It primarily focuses on how to use TLS to protect clients connecting to a web application over HTTPS, though much of this guidance is also applicable to other uses of TLS. When correctly implemented, TLS can provide several security benefits: Confidentiality: Provides protection against attackers reading the contents of the traffic. Integrity: Provides protection against traffic modification, such as an attacker replaying requests against the server. Authentication: Enables the client to confirm they are connected to the legitimate server. Note that the identity of the client is not verified unless client certificates are employed. SSL vs TLS Secure Socket Layer (SSL) was the original protocol that was used to provide encryption for HTTP traffic, in the form of HTTPS. There were two publicly released versions of SSL - versions 2 and 3. Both of these have serious cryptographic weaknesses and should no longer be used. For various reasons the next version of the protocol (...

INSECURE DEPLOYMENT : Unpatched Application

Summary   Failure to install up-to-date patches could lead to severe system compromise Explanation Third party applications, application servers, or web frameworks with known vulnerabilities expands the attack surface available to the attacker. Remedation Update the components that were identified by the pentester as potentially vulnerable. References:  https://owasp.org/Top10/A06_2021-Vulnerable_and_Outdated_Components/