Posts

Showing posts with the label Insecure Transport

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 Transport: Channel Mixing

Summary If a server has sensitive information on it that  hould only be exchanged via SSL, it should not be possible to access this information using a non-SSL connection. Explanation An attacker could potentially intercept sensitive data including usernames and passwords, customer account information, or similar information. Recommendation Disable the unencrypted web service. Examples: If you type a command:    curl -i yourdomain.com If it response "301 Moved Permanently" its means your server have channel Mixing. If your server reponse "Failed connect to <yourdomain.com> port 80: Connection timed out" its means your server is protected because your server don't permit connecions by port 80 (Not secure).