|2 via 2 paths|
Find, fix and prevent vulnerabilities in your code.
- Vulnerable module: adm-zip
- Introduced through: email@example.com
Introduced through: firstname.lastname@example.org › email@example.comRemediation: Upgrade to firstname.lastname@example.org.
Affected versions of this package are vulnerable to Directory Traversal. It could extract files outside the target folder.
A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.
Directory Traversal vulnerabilities can be generally divided into two types:
- Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.
st is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the
If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.
%2e is the URL encoded version of
- Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as
One way to achieve this is by using a malicious
zip archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.
The following is an example of a
zip archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in
/root/.ssh/ overwriting the
2018-04-15 22:04:29 ..... 19 19 good.txt 2018-04-15 22:04:42 ..... 20 20 ../../../../../../root/.ssh/authorized_keys
adm-zip to version 0.5.2 or higher.
- Vulnerable module: https-proxy-agent
- Introduced through: email@example.com
Introduced through: firstname.lastname@example.org › email@example.comRemediation: Upgrade to firstname.lastname@example.org.
https-proxy-agent is a module that provides an http.Agent implementation that connects to a specified HTTP or HTTPS proxy server, and can be used with the built-in https module.
Affected versions of this package are vulnerable to Man-in-the-Middle (MitM). When targeting a HTTP proxy,
https-proxy-agent opens a socket to the proxy, and sends the proxy server a
CONNECT request. If the proxy server responds with something other than a HTTP response
https-proxy-agent incorrectly returns the socket without any TLS upgrade. This request data may contain basic auth credentials or other secrets, is sent over an unencrypted connection. A suitably positioned attacker could steal these secrets and impersonate the client.
PoC by Kris Adler
var url = require('url'); var https = require('https'); var HttpsProxyAgent = require('https-proxy-agent'); var proxyOpts = url.parse('http://127.0.0.1:80'); var opts = url.parse('https://www.google.com'); var agent = new HttpsProxyAgent(proxyOpts); opts.agent = agent; opts.auth = 'username:password'; https.get(opts);
https-proxy-agent to version 2.2.3 or higher.