Telisca IPS Lock Cisco IP Phone Control - Metasploit
This page contains detailed information about how to use the auxiliary/voip/telisca_ips_lock_control metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Telisca IPS Lock Cisco IP Phone Control
Module: auxiliary/voip/telisca_ips_lock_control
Source code: modules/auxiliary/voip/telisca_ips_lock_control.rb
Disclosure date: 2015-12-17
Last modification time: 2022-04-21 13:31:55 +0000
Supported architecture(s): -
Supported platform(s): -
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: -
This module allows an unauthenticated attacker to exercise the "Lock" and "Unlock" functionality of Telisca IPS Lock for Cisco IP Phones. This module should be run in the VoIP VLAN, and requires knowledge of the target phone's name (for example, SEP002497AB1D4B). Set ACTION to either LOCK or UNLOCK. UNLOCK is the default.
Module Ranking and Traits
Module Ranking:
- normal: The exploit is otherwise reliable, but depends on a specific version and can't (or doesn't) reliably autodetect. More information about ranking can be found here.
Basic Usage
msf > use auxiliary/voip/telisca_ips_lock_control
msf auxiliary(telisca_ips_lock_control) > show targets
... a list of targets ...
msf auxiliary(telisca_ips_lock_control) > set TARGET target-id
msf auxiliary(telisca_ips_lock_control) > show options
... show and set options ...
msf auxiliary(telisca_ips_lock_control) > exploit
Required Options
RHOSTS: The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RHOST: The IPS Lock IP Address
PHONENAME: The name of the target phone
Go back to menu.
Msfconsole Usage
Here is how the voip/telisca_ips_lock_control auxiliary module looks in the msfconsole:
msf6 > use auxiliary/voip/telisca_ips_lock_control
msf6 auxiliary(voip/telisca_ips_lock_control) > show info
Name: Telisca IPS Lock Cisco IP Phone Control
Module: auxiliary/voip/telisca_ips_lock_control
License: Metasploit Framework License (BSD)
Rank: Normal
Disclosed: 2015-12-17
Provided by:
Fakhir Karim Reda <[email protected]>
zirsalem
Available actions:
Name Description
---- -----------
LOCK To lock a phone
UNLOCK To unlock a phone
Check supported:
No
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
PHONENAME yes The name of the target phone
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
RHOST yes The IPS Lock IP Address
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
VHOST no HTTP server virtual host
Description:
This module allows an unauthenticated attacker to exercise the
"Lock" and "Unlock" functionality of Telisca IPS Lock for Cisco IP
Phones. This module should be run in the VoIP VLAN, and requires
knowledge of the target phone's name (for example, SEP002497AB1D4B).
Set ACTION to either LOCK or UNLOCK. UNLOCK is the default.
Module Options
This is a complete list of options available in the voip/telisca_ips_lock_control auxiliary module:
msf6 auxiliary(voip/telisca_ips_lock_control) > show options
Module options (auxiliary/voip/telisca_ips_lock_control):
Name Current Setting Required Description
---- --------------- -------- -----------
PHONENAME yes The name of the target phone
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
RHOST yes The IPS Lock IP Address
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
VHOST no HTTP server virtual host
Auxiliary action:
Name Description
---- -----------
UNLOCK To unlock a phone
Advanced Options
Here is a complete list of advanced options supported by the voip/telisca_ips_lock_control auxiliary module:
msf6 auxiliary(voip/telisca_ips_lock_control) > show advanced
Module advanced options (auxiliary/voip/telisca_ips_lock_control):
Name Current Setting Required Description
---- --------------- -------- -----------
DOMAIN WORKSTATION yes The domain to use for Windows authentication
DigestAuthIIS true no Conform to IIS, should work for most servers. Only set to false for non-IIS servers
FingerprintCheck true no Conduct a pre-exploit fingerprint verification
HttpClientTimeout no HTTP connection and receive timeout
HttpPassword no The HTTP password to specify for authentication
HttpRawHeaders no Path to ERB-templatized raw headers to append to existing headers
HttpTrace false no Show the raw HTTP requests and responses
HttpTraceColors red/blu no HTTP request and response colors for HttpTrace (unset to disable)
HttpTraceHeadersOnly false no Show HTTP headers only in HttpTrace
HttpUsername no The HTTP username to specify for authentication
SSLVersion Auto yes Specify the version of SSL/TLS to be used (Auto, TLS and SSL23 are auto-negotiate) (Accepted: Auto, TLS, SSL23, SSL3, TLS1, TLS1.1, TLS1.2)
UserAgent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) no The User-Agent header to use for all requests
VERBOSE false no Enable detailed status messages
WORKSPACE no Specify the workspace for this module
Auxiliary Actions
This is a list of all auxiliary actions that the voip/telisca_ips_lock_control module can do:
msf6 auxiliary(voip/telisca_ips_lock_control) > show actions
Auxiliary actions:
Name Description
---- -----------
LOCK To lock a phone
UNLOCK To unlock a phone
Evasion Options
Here is the full list of possible evasion options supported by the voip/telisca_ips_lock_control auxiliary module in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 auxiliary(voip/telisca_ips_lock_control) > show evasion
Module evasion options:
Name Current Setting Required Description
---- --------------- -------- -----------
HTTP::header_folding false no Enable folding of HTTP headers
HTTP::method_random_case false no Use random casing for the HTTP method
HTTP::method_random_invalid false no Use a random invalid, HTTP method for request
HTTP::method_random_valid false no Use a random, but valid, HTTP method for request
HTTP::pad_fake_headers false no Insert random, fake headers into the HTTP request
HTTP::pad_fake_headers_count 0 no How many fake headers to insert into the HTTP request
HTTP::pad_get_params false no Insert random, fake query string variables into the request
HTTP::pad_get_params_count 16 no How many fake query string variables to insert into the request
HTTP::pad_method_uri_count 1 no How many whitespace characters to use between the method and uri
HTTP::pad_method_uri_type space no What type of whitespace to use between the method and uri (Accepted: space, tab, apache)
HTTP::pad_post_params false no Insert random, fake post variables into the request
HTTP::pad_post_params_count 16 no How many fake post variables to insert into the request
HTTP::pad_uri_version_count 1 no How many whitespace characters to use between the uri and version
HTTP::pad_uri_version_type space no What type of whitespace to use between the uri and version (Accepted: space, tab, apache)
HTTP::uri_dir_fake_relative false no Insert fake relative directories into the uri
HTTP::uri_dir_self_reference false no Insert self-referential directories into the uri
HTTP::uri_encode_mode hex-normal no Enable URI encoding (Accepted: none, hex-normal, hex-noslashes, hex-random, hex-all, u-normal, u-all, u-random)
HTTP::uri_fake_end false no Add a fake end of URI (eg: /%20HTTP/1.0/../../)
HTTP::uri_fake_params_start false no Add a fake start of params to the URI (eg: /%3fa=b/../)
HTTP::uri_full_url false no Use the full URL for all HTTP requests
HTTP::uri_use_backslashes false no Use back slashes instead of forward slashes in the uri
HTTP::version_random_invalid false no Use a random invalid, HTTP version for request
HTTP::version_random_valid false no Use a random, but valid, HTTP version for request
Go back to menu.
Error Messages
This module may fail with the following error messages:
Check for the possible causes from the code snippets below found in the module source code. This can often times help in identifying the root cause of the problem.
Connection failed
Here is a relevant code snippet related to the "Connection failed" error message:
65: res = send_request_raw({'method' => 'GET', 'uri' => '/'})
66: return true if res
67: rescue ::Rex::ConnectionRefused
68: vprint_status("Connection refused")
69: rescue ::Rex::ConnectionError
70: vprint_error("Connection failed")
71: rescue ::OpenSSL::SSL::SSLError
72: vprint_error("SSL/TLS connection error")
73: end
74:
75: false
SSL/TLS connection error
Here is a relevant code snippet related to the "SSL/TLS connection error" error message:
67: rescue ::Rex::ConnectionRefused
68: vprint_status("Connection refused")
69: rescue ::Rex::ConnectionError
70: vprint_error("Connection failed")
71: rescue ::OpenSSL::SSL::SSLError
72: vprint_error("SSL/TLS connection error")
73: end
74:
75: false
76: end
77:
Unexpected response <RES.CODE>
Here is a relevant code snippet related to the "Unexpected response <RES.CODE>" error message:
103: print_good("The device #{phone_name} is already locked")
104: elsif res.body.include?('unlocked') || res.body.include?('Locking') || res.body.include?('QUIT')
105: print_good("Device #{phone_name} successfully locked")
106: end
107: elsif res
108: print_error("Unexpected response #{res.code}")
109: else
110: print_error('The connection timed out while trying to lock.')
111: end
112: end
113:
The connection timed out while trying to lock.
Here is a relevant code snippet related to the "The connection timed out while trying to lock." error message:
105: print_good("Device #{phone_name} successfully locked")
106: end
107: elsif res
108: print_error("Unexpected response #{res.code}")
109: else
110: print_error('The connection timed out while trying to lock.')
111: end
112: end
113:
114:
115: # Unlocks a phone.
Unexpected response <RES.CODE>
Here is a relevant code snippet related to the "Unexpected response <RES.CODE>" error message:
137: print_good("The device #{phone_name} is already locked")
138: elsif res.body.include?('unlocked') || res.body.include?('QUIT')
139: print_good("The device #{phone_name} successfully unlocked")
140: end
141: elsif res
142: print_error("Unexpected response #{res.code}")
143: else
144: print_error('The connection timed out while trying to unlock')
145: end
146: end
147:
The connection timed out while trying to unlock
Here is a relevant code snippet related to the "The connection timed out while trying to unlock" error message:
139: print_good("The device #{phone_name} successfully unlocked")
140: end
141: elsif res
142: print_error("Unexpected response #{res.code}")
143: else
144: print_error('The connection timed out while trying to unlock')
145: end
146: end
147:
148:
149: def run
The web server is unreachable!
Here is a relevant code snippet related to the "The web server is unreachable!" error message:
146: end
147:
148:
149: def run
150: unless port_open?
151: print_error('The web server is unreachable!')
152: return
153: end
154:
155: phone_name = datastore['PHONENAME']
156: case action.name
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #8716 Merged Pull Request: Print_Status -> Print_Good (And OCD bits 'n bobs)
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #6655 Merged Pull Request: use MetasploitModule as a class name
- #6648 Merged Pull Request: Change metasploit class names
- #6470 Merged Pull Request: Add module Telisca IPS Lock/Unlock
Go back to menu.
See Also
Check also the following modules related to this module:
- auxiliary/voip/asterisk_login
- auxiliary/voip/cisco_cucdm_call_forward
- auxiliary/voip/cisco_cucdm_speed_dials
- auxiliary/voip/sip_deregister
- auxiliary/voip/sip_invite_spoof
- auxiliary/scanner/misc/clamav_control
- auxiliary/scanner/misc/poisonivy_control_scanner
- exploit/multi/http/zenworks_control_center_upload
- exploit/windows/http/sap_host_control_cmd_exec
- exploit/windows/http/sharepoint_unsafe_control
- exploit/windows/misc/remote_control_collection_rce
- exploit/windows/scada/sunway_force_control_netdbsrv
- auxiliary/scanner/http/meteocontrol_weblog_extractadmin
- exploit/linux/http/f5_icontrol_exec
- exploit/linux/http/f5_icontrol_rce
- exploit/linux/http/f5_icontrol_rest_ssrf_rce
- exploit/linux/http/f5_icontrol_rpmspec_rce_cve_2022_41800
- exploit/linux/http/f5_icontrol_soap_csrf_rce_cve_2022_41622
- exploit/linux/http/symantec_web_gateway_pbcontrol
- exploit/unix/webapp/zoneminder_packagecontrol_exec
- exploit/windows/browser/crystal_reports_printcontrol
- exploit/windows/local/ntapphelpcachecontrol
- exploit/windows/nimsoft/nimcontroller_bof
- auxiliary/scanner/http/rips_traversal
- auxiliary/scanner/tftp/ipswitch_whatsupgold_tftp
- auxiliary/admin/http/linksys_tmunblock_admin_reset_bof
Authors
- Fakhir Karim Reda <karim.fakhir[at]gmail.com>
- zirsalem
Version
This page has been produced using Metasploit Framework version 6.2.29-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.
