Posts

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/

Apache header directives for security

This is a list of header directives for to increment security site. You have two ways for set this security header, from .htacess or from your web server. Example using ".htaccess"  <IfModule mod_headers.c>      Header set X-Frame-Options "DENY"  </IfModule>   You can set using "Header set" followed by header policy.  This is a list from more commons.   Content-Security-Policy Examples 1  <IfModule mod_headers.c>     Header set Content-Security-Policy "default-src 'self' style-src 'self' 'unsafe-inline' fonts.googleapis.com script-src 'self' font-src 'self' fonts.gstatic.com "  </IfModule>   You can find a complete documentation on this link:  Directives for bootstrap  https://content-security-policy.com/examples/google-fonts/ https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy  Strict Transp...

Code Correctness: Untested Functionality

Summary During security testing of the target application, some of the functionality was found to be inoperable. As such, any potential security vulnerabilities associated with this functionality could not be evaluated and its controls could not be verified. Explanation Gaps in testing coverage could leave significant vulnerabilities unreported, leading to a false sense of security while leaving the application open to attack and/or compromise. Recommendation Ensure that all key application functionality is operational and ready for security testing to ensure completeness of coverage.

Poor Error Handling: Unhandled Exception

Summary Unhandled exceptions are circumstances in which the application has received user input that it did not expect and does not know how to handle. When successfully exploited, an attacker can gain unauthorized access to the database by using the information recovered from seemingly innocuous error messages to pinpoint flaws in the web application and to discover additional  venues of attack. Recommendations include designing and adding consistent error-handling mechanisms that are capable of handling any user input to your web application, providing meaningful detail to end-users, and preventing error messages that might provide information useful to an attacker from being displayed. Description The most common cause of an unhandled exception is a failure to properly sanitize client-supplied data that is used in SQL statements. They can also be caused by a bug in the web application's database communication code, a misconfiguration of database connection settings, an unavailab...