Nmap http-icloud-sendmsg NSE Script


This page contains detailed information about how to use the http-icloud-sendmsg NSE script. For list of all NSE scripts, visit the Nmap NSE Library.

Select:
Overview
Error Messages

Script Overview

Script source code: https://github.com/nmap/nmap/tree/master/scripts/http-icloud-sendmsg.nse
Script categories: discovery, safe, external
Target service / protocol: -
Target network port(s): -
List of CVEs: -

Script Description

The http-icloud-sendmsg.nse script sends a message to a iOS device through the Apple MobileMe web service. The device has to be registered with an Apple ID using the Find My Iphone application.

Http-icloud-sendmsg NSE Script Arguments

This is a full list of arguments supported by the http-icloud-sendmsg.nse script:

http-icloud-sendmsg.deviceindex

The device index to which the message should be sent (@see http-icloud-sendmsg.listdevices)

http-icloud-sendmsg.listdevices

List the devices managed by the specified Apple ID.

http-icloud-sendmsg.message

The body of the message to send to the device.

http-icloud-sendmsg.password

The Apple ID password

http-icloud-sendmsg.sound

Boolean specifying if a loud sound should be played while displaying the message. (default: true)

http-icloud-sendmsg.subject

The subject of the message to send to the device.

http-icloud-sendmsg.username

The Apple ID username

smbdomain

The domain to log in with. If you aren't in a domain environment, then anything will (should?) be accepted by the server.

smbhash

A password hash to use when logging in. This is given as a single hex string (32 characters) or a pair of hex strings (both 32 characters, optionally separated by a single character). These hashes are the LanMan or NTLM hash of the user's password, and are stored on disk or in memory. They can be retrieved from memory using the fgdump or pwdump tools.

smbnoguest

Use to disable usage of the 'guest' account.

smbpassword

The password to connect with. Be cautious with this, since some servers will lock accounts if the incorrect password is given. Although it's rare that the Administrator account can be locked out, in the off chance that it can, you could get yourself in trouble. To use a blank password, leave this parameter off altogether.

smbtype

The type of SMB authentication to use. These are the possible options:

  • v1: Sends LMv1 and NTLMv1.
  • LMv1: Sends LMv1 only.
  • NTLMv1: Sends NTLMv1 only (default).
  • v2: Sends LMv2 and NTLMv2.
  • LMv2: Sends LMv2 only.
  • NTLMv2: Doesn't exist; the protocol doesn't support NTLMv2 alone. The default, NTLMv1, is a pretty decent compromise between security and compatibility. If you are paranoid, you might want to use v2 or lmv2 for this. (Actually, if you're paranoid, you should be avoiding this protocol altogether!). If you're using an extremely old system, you might need to set this to v1 or lm, which are less secure but more compatible. For information, see smbauth.lua.

smbusername

The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN" are not understood. To set a domain, use the smbdomain argument.

slaxml.debug

Debug level at which default callbacks will print detailed parsing info. Default: 3

http.host

The value to use in the Host header of all requests unless otherwise set. By default, the Host header uses the output of stdnse.get_hostname().

http.max-body-size

Limit the received body to specific number of bytes. An oversized body results in an error unless script argument http.truncated-ok or request option truncated_ok is set to true. The default is 2097152 (2MB). Use value -1 to disable the limit altogether. This argument can be overridden case-by-case with request option max_body_size.

http.max-cache-size

The maximum memory size (in bytes) of the cache.

http.max-pipeline

If set, it represents the number of outstanding HTTP requests that should be sent together in a single burst. Defaults to http.pipeline (if set), or to what function get_pipeline_limit returns.

http.pipeline

If set, it represents the number of HTTP requests that'll be sent on one connection. This can be set low to make debugging easier, or it can be set high to test how a server reacts (its chosen max is ignored).

http.truncated-ok

Do not treat oversized body as error. (Use response object flag truncated to check if the returned body has been truncated.) This argument can be overridden case-by-case with request option truncated_ok.

http.useragent

The value of the User-Agent header field sent with requests. By default it is "Mozilla/5.0 (compatible; Nmap Scripting Engine; https://nmap.org/book/nse.html)". A value of the empty string disables sending the User-Agent header field.

- - -
To use these script arguments, add them to the Nmap command line using the --script-args arg1=value,[arg2=value,..] syntax. For example:

nmap --script=http-icloud-sendmsg --script-args http-icloud-sendmsg.deviceindex=value,http-icloud-sendmsg.listdevices=value <target>

Http-icloud-sendmsg NSE Script Example Usage

Here's an example of how to use the http-icloud-sendmsg.nse script:

nmap -sn -Pn --script http-icloud-sendmsg --script-args="username=<user>,password=<pass>,http-icloud-sendmsg.listdevices"

nmap -sn -Pn --script http-icloud-sendmsg --script-args="username=<user>,password=<pass>,deviceindex=1,subject='subject',message='hello world.',sound=false"

Http-icloud-sendmsg NSE Script Example Output

Here's a sample output from the http-icloud-sendmsg.nse script:

Pre-scan script results:
| http-icloud-sendmsg:
|_  Message was successfully sent to "Patrik Karlsson's iPhone"

Http-icloud-sendmsg NSE Script Example XML Output

There is no sample XML output for this module. However, by providing the -oX <file> option, Nmap will produce a XML output and save it in the file.xml file.

Author

  • Patrik Karlsson

References

See Also

Related NSE scripts to the http-icloud-sendmsg.nse script:

Visit Nmap NSE Library for more scripts.

The http-icloud-sendmsg.nse script may fail with the following error messages. Check for the possible causes by using the code snippets highlighted below found in the script source code. This can often times help in identifying the root cause of the problem.

Failed to get devices

Here is a relevant code snippet related to the "Failed to get devices" error message:

61:	local function fail(err) return stdnse.format_output(false, err) end
62:	
63:	local function listDevices(mm)
64:	  local status, devices = mm:getDevices()
65:	  if ( not(status) ) then
66:	    return fail("Failed to get devices")
67:	  end
68:	
69:	  local output = tab.new(2)
70:	  tab.addrow(output, "id", "name")
71:	  for i=1, #devices do

No username or password was supplied

Here is a relevant code snippet related to the "No username or password was supplied" error message:

79:	end
80:	
81:	
82:	action = function()
83:	  if ( not(arg_username) or not(arg_password) ) then
84:	    return fail("No username or password was supplied")
85:	  end
86:	
87:	  if ( not(arg_deviceindex) and not(arg_listdevices) ) then
88:	    return fail("No device ID was specified")
89:	  end

No device ID was specified

Here is a relevant code snippet related to the "No device ID was specified" error message:

83:	  if ( not(arg_username) or not(arg_password) ) then
84:	    return fail("No username or password was supplied")
85:	  end
86:	
87:	  if ( not(arg_deviceindex) and not(arg_listdevices) ) then
88:	    return fail("No device ID was specified")
89:	  end
90:	
91:	  if ( 1 == tonumber(arg_listdevices) or "true" == arg_listdevices ) then
92:	    local mm = mobileme.Helper:new(arg_username, arg_password)
93:	    return listDevices(mm)

Missing subject or message

Here is a relevant code snippet related to the "Missing subject or message" error message:

90:	
91:	  if ( 1 == tonumber(arg_listdevices) or "true" == arg_listdevices ) then
92:	    local mm = mobileme.Helper:new(arg_username, arg_password)
93:	    return listDevices(mm)
94:	  elseif ( not(arg_subject) or not(arg_message) ) then
95:	    return fail("Missing subject or message")
96:	  else
97:	    local mm = mobileme.Helper:new(arg_username, arg_password)
98:	    local status, devices = mm:getDevices()
99:	
100:	    if ( not(status) ) then

Failed to get devices

Here is a relevant code snippet related to the "Failed to get devices" error message:

96:	  else
97:	    local mm = mobileme.Helper:new(arg_username, arg_password)
98:	    local status, devices = mm:getDevices()
99:	
100:	    if ( not(status) ) then
101:	      return fail("Failed to get devices")
102:	    end
103:	
104:	    if ( status and arg_deviceindex <= #devices ) then
105:	      local status = mm:sendMessage( devices[arg_deviceindex].id, arg_subject, arg_message, arg_sound)
106:	      if ( status ) then

n Failed to send message

Here is a relevant code snippet related to the "n Failed to send message" error message:

103:	
104:	    if ( status and arg_deviceindex <= #devices ) then
105:	      local status = mm:sendMessage( devices[arg_deviceindex].id, arg_subject, arg_message, arg_sound)
106:	      if ( status ) then
107:	        return ("\n  Message was successfully sent to "%s""):format(decodeString(devices[arg_deviceindex].name or ""))
108:	      else
109:	        return "\n  Failed to send message"
110:	      end
111:	    end
112:	  end
113:	end

Version

This page has been created based on Nmap version 7.92.

Go back to menu.