Clear-text protocols as ftp, telnet or non secure http are lacking encryption of transported data. They are
also missing the capability to build an authenticated connection. This mean that any attacker who can sniff traffic from the network can read, modify
or corrupt the transported content. These protocol are not secure as they expose applications to a large range of risk:
Note also that using the http protocol is being deprecated by major web browser.
In the past, it has led to the following vulnerabilities:
There is a risk if you answered yes to any of those questions.
ssh as an alternative to telnet sftp, scp or ftps instead of ftp https instead of http SMTP over SSL/TLS or SMTP with STARTTLS instead of clear-text SMTP It is recommended to secure all transport channels (event local network) as it can take a single non secure connection to compromise an entire application or system.
$url = "http://example.com"; // Sensitive
$url = "ftp://anonymous@example.com"; // Sensitive
$url = "telnet://anonymous@example.com"; // Sensitive
$con = ftp_connect('example.com'); // Sensitive
$trans = (new Swift_SmtpTransport('XXX', 1234)); // Sensitive
$mailer = new PHPMailer(true); // Sensitive
$url = "https://example.com"; // Compliant
$url = "sftp://anonymous@example.com"; // Compliant
$url = "ssh://anonymous@example.com"; // Compliant
$con = ftp_ssl_connect('example.com'); // Compliant
$trans = (new Swift_SmtpTransport('smtp.example.org', 1234))
->setEncryption('tls') // Compliant
;
$mailer = new PHPMailer(true);
$mailer->SMTPSecure = 'tls'; // Compliant
No issue is reported for the following cases because they are not considered sensitive:
localhost