IMPACT AND RISK
Since the attack is so widespread, since its purpose cannot be truly uncovered, and since each target network is different both in purpose and in layout, no one statement can be made about impact and risk.
As noted below, botnets that dial communication protocols over and over to as many hosts as possible are quite likely looking for a means to conduct toll fraud – dialing calls through third-party systems, without the consent of the owners of those third-party systems.
Last Update: 3/8/2022
Initial Public Release: 11/18/2014
Advisory ID: PLYGN14-23
A “botnet”, or mass group of systems on the Internet under the control of one or several malicious entities, is being used to place calls to any device on the Internet that can meaningfully respond to an H.323 or SIP call. This means endpoints, bridges, MCU’s, gatekeepers, firewalls, proxies, etc. might all be called by the botnet.
The purpose of the botnet is unclear, although toll fraud is usually the purpose behind such broad sweeps against systems that speak a specific communications protocol. The systems used in the botnet are, as is typical with this method, innocent third-party hosts whose owners are most likely unaware are a part of the botnet.
The botnet can successfully be run against all H.323 and SIP systems it finds on the Internet and is presumably noting which systems respond to calls for future attacks.
One particular botnet advertises itself by the fact that it seems to consistently use “h323-ID = ‘cisco’”. The name appears to be unrelated to anything in the real world and is rather a way of adding seeming legitimacy to the H.323 botnet. Others seen more recently are simply using an IP address for the h323-ID.
The botnet appears to be at least partially (probably mostly) comprised of web servers around the Internet, all of which appear to be operating below recommended security patch levels. Such systems are owned by innocent third parties who do not patch their systems to current levels. The attackers first use known security flaws to compromise such systems, and then insert code that dials H.323 and SIP systems and reports back to the individual(s) who created this illegal system (“bot master” and “bot herder” are the normal terms for the one(s) in control of the botnet).
Every system we have been able to analyze (but one) conforms with this model. One of the IP addresses used to call H.323 systems was analyzed and is shown below. The one system that did not conform with the under-patched web server model was an instance of FreePBX – most likely compromised in a similar manner for identical purposes.
From the perspective of the Internet, this is just a random web server whose owner failed to patch things when known vulnerabilities were announced (we had permission to scan). Such systems might be behind on patching Apache or OpenSSL or other similar modules. This one (as reported by Nikto, a free vulnerability scanner) has a vulnerability from 2002 among its many vulnerabilities.
Again, this is NOT a “bad guy” system. This is a third-party web server, poorly maintained, compromised by the attacker(s), and then loaded with the software that is performing the calls:
Poly cannot give advice on specific firewall configurations or specific firewalls. Those who have a third-party firewall as their defense against incoming H.323 calls should consult with their firewall and/or security experts before implementing any of the high-level recommendation in this advisory.
H.323 is not traditionally a firewall-friendly protocol. H.323 uses both UDP and TCP over a range of ports both static and dynamic. Firewalls that support H.323 natively include special rules or modules to deal with the nuances of the H.323 protocol. Such firewalls might be able to use the field information above in the form of rules or ACL’s.
Alternatively, a firewall can come at the problem with more traditional IP-based whitelisting or blacklisting techniques.
RealPresence Access Director (RPAD):
RPAD administrators can make rules to enable blocking for the two fields listed above.
The since the release of software version 4.2.2, RPAD improves these rules and administrators should ensure they’re running this or later versions.
There are several malicious H.323 agents that can cause problems for customer environments. The table below lists some of the more common agents.
|MERA RTU||request.endpointVendor.productId||==||MERA RTU|
The rule for Product ID of “ooh323” is shown here below. Similar rules should be set for other agents.
There are a growing number of malicious SIP agents that can cause problems with customer environments. The table below lists some of the more common malicious SIP agents.
|VoIP v11.1.2||request.user-agent||==(case-insensitive)||VoIP v11.1.2|
|FreePBX 1.8||request.user-agent||==(case-insensitive)||FreePBX 1.8|
The rule for SIP agent “friendly-scanner” is shown here below. Similar rules should be set for other malicious SIP agents.
Video Border Proxy (VBP):
VBP version 11.2.20 has fixed the issue without need for any configuration changes. This version disables fastStart on the WAN side when the call originates from a non-registered client.
This change appears to reduce the nuisance factor of the H.323 botnet without the need for configuration changes.
The challenge with these scenarios is that the target hosts (all H.323 and SIP-listening devices) are doing exactly what they are set up to do: answering calls. Polycom products are not vulnerable to anything in this situation. Mitigations to relieve the burden presented by these non-stop calls therefore come in the form of adding some ability to discern desired calls from undesired calls.
Whitelisting is the most common method for separating the good calls from the bad. In an environment where all of the “good guys” are known, it is best to simply create whitelists comprised of those addresses, and to deny all inbound calls NOT from those addresses.
Other times blacklists can be grown and maintained, blocking each of the botnet callers as it is logged and confirmed to be a “bad guy”.
The initial botnet has consistently populated two key H.323 fields with the same information.
- H.323 Alias Value: (h323-ID = “cisco”)
- Vendor Product ID Field: (productId = “ooh323”)
A newer variant has changed this, using an IP address for its h323-ID field but consistently populates the productId field with “MERA RTU”
- H.323 Alias Value: (h323-ID = random IP address)
- Vendor Product ID Field: (productId = “MERA RTU”)
The below RPAD screenshot taken from an RPAD management interface
shows both fields from the initial botnet findings:
The latest variant of the botnet can be seen using “MERA RTU” in
the RPAD screenshot below:
Any customer using an affected system who is concerned about this vulnerability within their deployment should contact Poly Technical Support – (888) 248-4143, (916) 928-7561, or visit the Poly Support Site.
|1.1||5/6/2015||Clarification on advisory/bulletindifferences and inclusion of h323-ID = “cisco” string earlier in the document.|
|1.2||12/16/2015||Updated bulletin to address currentattacks and defense configurations for “MERA RTU”.|
|1.3||3/15/2017||Updated bulletin to address currentattacks and defense configurations for H.323 and SIP.|
|1.4||3/21/2017||Updated bulletin to add additionalH.323 and SIP agents.|
|1.5||11/18/2017||Updated bulletin to add additionalH.323 and SIP agents.|
|1.6||1/14/2020||Corrected some settings and updatedformat for Poly.|
©2022 Plantronics, Inc. All rights reserved.
Poly, the propeller design, and the Poly logo are trademarks of Plantronics, Inc. All other trademarks are property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express written permission of Poly.
While Poly uses reasonable efforts to include accurate and up-to-date information in this document, Poly makes no warranties or representations as to its accuracy. Poly assumes no liability or responsibility for any typographical errors, out of date information, or any errors or omissions in the content of this document. Poly reserves the right to change or update this document at any time. Individuals are solely responsible for verifying that they have and are using the most recent Technical Bulletin.
Limitation of Liability
Poly and/or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose. Information is provided "as is" without warranty of any kind and is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall Poly and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive, or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of business information), even if Poly has been advised of the possibility of such damages.