A customer with a SIP enabled PBX server behind a Fortigate (5.2.9) with an outbound only policy to allow connection to an external SIP provider recently experienced VoIP fraud. Upon investigating and opening a ticket with Fortinet support it was discovered that SIP ALG will allow unsolicited connections in on port 5060.
You can replicate this yourself:
[ul]As per Fortinet support this is the default and expected behaviour. I tried at length to explain to them that allowing unsolicited inbound connections in on an outbound isn't acceptable. They referred me to the documentation which states:
When register is going through the FortiGate with SIP ALG enabled; it will create a pinhole in the reverse direction allowing all SIP packets to be forwarded inside the network; whatever the source address it comes from. The pinhole created will skip the firewall checking in the reverse direction. Because of this, there is no way to filter some IP addresses.
This fix is to enable strict-register.
I really believe Fortinet need to change this default behaviour. Already since my original ticket I've heard of another Foritigate owner who lost USD$20000 in VoIP fraud due to this. Of course customers should also do more to secure their PBX, but who expects unsolicited inbound connections on an outbound policy?
You can read more here:
[ul]
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1712 | |
1093 | |
752 | |
447 | |
231 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.