New answers tagged known-vulnerabilities
Whilst the lack of SSL/TLS or other transport security is definitely an issue, it is important to note that there's nothing here to suggest that your Pure-FTP server is misconfigured. You are meant to see this prompt before you authenticate against the server (username/password). It might be worth checking that you can't login by typing "Anonymous" at this ...
To echo Gowenfawr, if you don't need it, disable/uninstall it. However if you do need FTP then there are some things you can do to control access. Review the FTP configuration to make sure permissions are as granular as possible. Look at the user rights for ftp to see what directories are allowed for those users. Limit them as much as possible. If the ...
FTP is a very old protocol and not recommended anymore today because credentials are transmitted in plaintext which can be read by sniffing the network traffic. If you don't need it you should uninstall it or you can block this port with a firewall. On Linux you could use iptables to block all traffic to this port as follows: iptables -A INPUT -p tcp ...
You can't secure FTP. Remove it and replace with a secure alternative like SFTP if you need file transfer. The way in which you've asked the question implies that you don't have a valid need for it, that it's probably just on by default. Depending on what you're running, 'rpm -e pure-ftpd' or 'dpkg -r pure-ftpd' might do for you.
For this module in Metasploit (exploit/unix/webapp/joomla_tinybrowser), you'll need to target the endpoint from which the Joomla site is accessible, in this case the Apache server. You can set the Apache server's IP for the RHOST option, and then the required hostname for the VHOST option. VHOST essentially populates the Host HTTP header which will probably ...
Perhaps check it's checksum against the list at the bottom of http://speedutilities.com/process/lsass.exe.htm (courtesy of wikipedia)
You should search for "vulnerability database" before asking this question. Here are some answers: http://web.nvd.nist.gov/view/vuln/search http://cve.mitre.org/cve/ hxxp://osvdb.org/
Your question is a bit too broad and a bit opinion-based. That's why this is not a full answer. PHP has its downsides, and so pretty much every other language. Intrinsically, PHP isn't tangibly less secure than other languages in the same field. PHP has its built-in database abstraction layer PDO that has anti-SQL-injection features such as parameterized ...
Top 50 recent answers are included