{"id":4049,"date":"2016-01-14T01:55:11","date_gmt":"2016-01-13T17:55:11","guid":{"rendered":"https:\/\/www.darknet.org.uk\/?p=4049"},"modified":"2016-01-14T01:58:22","modified_gmt":"2016-01-13T17:58:22","slug":"fortinet-ssh-backdoor-found-firewalls","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2016\/01\/fortinet-ssh-backdoor-found-firewalls\/","title":{"rendered":"Fortinet SSH Backdoor Found In Firewalls"},"content":{"rendered":"

So the Fortinet SSH Backdoor, apparently it’s just a management authentication issue. Sorry, what’s that? It looks like a passphrase based admin level access login via SSH to me personally.<\/p>\n

Which is scary.<\/p>\n

\"Fortinet<\/p>\n

They are adamantly shouting from rooftops that it was not planted by a 3rd party (NSA? Like Juniper<\/a>..) or any kind of malicious activity.<\/p>\n

Enterprise security vendor Fortinet has attempted to explain why its FortiOS firewalls were shipped with hardcoded SSH logins.<\/p>\n

It appears Fortinet’s engineers implemented their own method of authentication for logging-into FortiOS-powered devices, and the mechanism ultimately uses a secret passphrase. This code was reverse-engineered by persons unknown, and a Python script to exploit the hole emerged on the Full Disclosure mailing list this week.<\/p>\n

Anyone who uses this script against vulnerable firewalls will gain administrator-level command-line access to the equipment. After some outcry on Twitter and beyond, Fortinet responded by saying it has already killed off the dodgy login system.<\/p>\n

“This issue was resolved and a patch was made available in July 2014 as part of Fortinet’s commitment to ensuring the quality and integrity of our codebase,” a spokeswoman told El Reg.<\/p>\n

“This was not a ‘backdoor’ vulnerability issue but rather a management authentication issue. The issue was identified by our product security team as part of their regular review and testing efforts. After careful analysis and investigation, we were able to verify this issue was not due to any malicious activity by any party, internal or external.”<\/p>\n

In a security advisory dated today, Fortinet explained that the issue affects FortiOS versions 4.3.0 to 4.3.16 and 5.0.0 to 5.0.7. This covers FortiOS builds from between November 2012 and July 2014, and it’s certainly possible that some slack IT admins haven’t updated the software since then.<\/p><\/blockquote>\n