Fortinet removes SSH and database backdoors from its SIEM product
zdnet.com
zdnet.com
> "FortiSIEM has a hardcoded SSH public key for user 'tunneluser' which is the same between all installs," said Andrew Klaus, the security researcher who identified this issue.
What other horrible assumptions have been hardcoded into this product that we have yet to discover?
Somebody coded this in, code has been reviewed, managers approved the time spent on this, meetings held, etc. There is a git commit (or CVS, who knows) with the name and a ticket number.
Right now there are probably urgent meetings being held between the interested parties to re-introduce a similar access feature back to the code base, using maybe a password derived from an ip address or serial number.