Find, fix and prevent vulnerabilities in your code.
medium severity
- Vulnerable module: vue-template-compiler
- Introduced through: vite-plugin-dts@3.9.1, @xascode/chalk@0.1.1 and others
Detailed paths
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › vite-plugin-dts@3.9.1 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › vite-plugin-dts@3.9.1 › vue-tsc@1.8.27 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › vite-plugin-dts@3.9.1 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › vue-tsc@1.8.27 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › vite-plugin-dts@3.9.1 › vue-tsc@1.8.27 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › vue-tsc@1.8.27 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
Overview
vue-template-compiler is a template compiler for Vue 2.0
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) through the manipulation of object properties such as Object.prototype.staticClass or Object.prototype.staticStyle. An attacker can execute arbitrary JavaScript code by altering the prototype chain of these properties.
Note: This vulnerability is not present in Vue 3.
PoC
<head>
<script>
window.Proxy = undefined // Not necessary, but helpfull in demonstrating breaking out into `window.alert`
Object.prototype.staticClass = `alert("Polluted")`
</script>
<script src="https://cdn.jsdelivr.net/npm/vue@2.7.16/dist/vue.js"></script>
</head>
<body>
<div id="app"></div>
<script>
new window.Vue({
template: `<div class="">Content</div>`,
}).$mount('#app')
</script>
</body>
Details
Cross-site scripting (or XSS) is a code vulnerability that occurs when an attacker “injects” a malicious script into an otherwise trusted website. The injected script gets downloaded and executed by the end user’s browser when the user interacts with the compromised website.
This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.
Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.
Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as < and > can be coded as > in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.
The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.
Types of attacks
There are a few methods by which XSS can be manipulated:
| Type | Origin | Description |
|---|---|---|
| Stored | Server | The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link. |
| Reflected | Server | The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser. |
| DOM-based | Client | The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data. |
| Mutated | The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters. |
Affected environments
The following environments are susceptible to an XSS attack:
- Web servers
- Application servers
- Web application environments
How to prevent
This section describes the top best practices designed to specifically protect your code:
- Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
- Convert special characters such as
?,&,/,<,>and spaces to their respective HTML or URL encoded equivalents. - Give users the option to disable client-side scripts.
- Redirect invalid requests.
- Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
- Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
- Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.
Remediation
A fix was pushed into the master branch but not yet published.
References
medium severity
new
- Vulnerable module: vite
- Introduced through: vite@4.5.14, @xascode/chalk@0.1.1 and others
Detailed paths
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › vite@4.5.14Remediation: Upgrade to vite@5.4.21.
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @xascode/chalk@0.1.1 › vite@4.5.14
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › vite@4.5.14
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › @xascode/chalk@0.1.1 › vite@4.5.14
Overview
vite is a Native-ESM powered web dev build tool
Affected versions of this package are vulnerable to Directory Traversal via the server.fs.deny function. An attacker can access restricted files by appending a backslash to the URL when the development server is running on Windows and is explicitly exposed to the network.
Note:
This is only exploitable if the server is explicitly exposed to the network using the command line parameter --host or the config option server.host.
PoC
npm create vite@latest
cd vite-project/
cat "secret" > .env
npm install
npm run dev
curl --request-target /.env\ http://localhost:5173
Details
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 public route.
If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.
curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa
Note %2e is the URL encoded version of . (dot).
- Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as
Zip-Slip.
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 authorized_keys file:
2018-04-15 22:04:29 ..... 19 19 good.txt
2018-04-15 22:04:42 ..... 20 20 ../../../../../../root/.ssh/authorized_keys
Remediation
Upgrade vite to version 5.4.21, 6.4.1, 7.0.8, 7.1.11 or higher.
References
medium severity
new
- Vulnerable module: validator
- Introduced through: vite-plugin-dts@3.9.1, @xascode/chalk@0.1.1 and others
Detailed paths
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @microsoft/api-extractor-model@7.28.13 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @rushstack/terminal@0.10.0 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @microsoft/api-extractor-model@7.28.13 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @microsoft/api-extractor-model@7.28.13 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @rushstack/ts-command-line@4.19.1 › @rushstack/terminal@0.10.0 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @rushstack/terminal@0.10.0 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @rushstack/terminal@0.10.0 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @microsoft/api-extractor-model@7.28.13 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @rushstack/ts-command-line@4.19.1 › @rushstack/terminal@0.10.0 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @rushstack/ts-command-line@4.19.1 › @rushstack/terminal@0.10.0 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @rushstack/terminal@0.10.0 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › @microsoft/api-extractor@7.43.0 › @rushstack/ts-command-line@4.19.1 › @rushstack/terminal@0.10.0 › @rushstack/node-core-library@4.0.2 › z-schema@5.0.6 › validator@13.15.15
Overview
validator is a library of string validators and sanitizers.
Affected versions of this package are vulnerable to Improper Validation of Specified Type of Input. The isURL() function in the validator module parses and validates protocols in URLs using the following method
Remediation
A fix was pushed into the master branch but not yet published.
References
low severity
- Vulnerable module: vite
- Introduced through: vite@4.5.14, @xascode/chalk@0.1.1 and others
Detailed paths
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › vite@4.5.14Remediation: Upgrade to vite@5.4.20.
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @xascode/chalk@0.1.1 › vite@4.5.14
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › vite@4.5.14
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › @xascode/chalk@0.1.1 › vite@4.5.14
Overview
vite is a Native-ESM powered web dev build tool
Affected versions of this package are vulnerable to Relative Path Traversal via improper enforcement of server.fs settings. An attacker can access arbitrary HTML files on the server by sending crafted requests to the preview server.
Note:
This is only exploitable if the server is explicitly exposed to the network using the --host flag or the server.host configuration option, and the application uses appType set to 'spa' (default) or 'mpa'.
Remediation
Upgrade vite to version 5.4.20, 6.3.6, 7.0.7, 7.1.5 or higher.
References
low severity
- Vulnerable module: vue-template-compiler
- Introduced through: vite-plugin-dts@3.9.1, @xascode/chalk@0.1.1 and others
Detailed paths
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › vite-plugin-dts@3.9.1 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › vite-plugin-dts@3.9.1 › vue-tsc@1.8.27 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › vite-plugin-dts@3.9.1 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › vue-tsc@1.8.27 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › vite-plugin-dts@3.9.1 › vue-tsc@1.8.27 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
-
Introduced through: terrafile@xascode/terrafile#2389f030a68ce3a44a3512eceb974e36c4a5b276 › @jestaubach/terrafile-backend-lib@0.1.8 › @xascode/chalk@0.1.1 › vite-plugin-dts@3.9.1 › vue-tsc@1.8.27 › @vue/language-core@1.8.27 › vue-template-compiler@2.7.16
Overview
vue-template-compiler is a template compiler for Vue 2.0
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) through the parseHTML function in html-parser.ts. An attacker can cause the application to consume excessive resources by supplying a specially crafted input that triggers inefficient regular expression evaluation.
PoC
Within Vue 2 client-side application code, create a new Vue instance with a template string that includes a <script> node tag that has a different closing tag (in this case </textarea>).
new Vue({
el: '#app',
template: '
<div>
Hello, world!
<script>${'<'.repeat(1000000)}</textarea>
</div>'
});
Set up an index.html file that loads the above JavaScript and then mount the newly created Vue instance with mount().
<!DOCTYPE html>
<html>
<head>
<title>My first Vue app</title>
</head>
<body>
<div id="app">
Loading..
</div>
</body>
</html>
In a browser, visit your Vue application
http://localhost:3000
In the browser, observe how the ReDoS vulnerability is able to increase the amount of time it takes for the page to parse the template and mount your Vue application. This demonstrates the ReDoS vulnerability.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the+matches one or more times). The+at the end of this section states that we can look for one or more matches of this section.DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
| String | Number of C's | Number of steps |
|---|---|---|
| ACCCX | 3 | 38 |
| ACCCCX | 4 | 71 |
| ACCCCCX | 5 | 136 |
| ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
There is no fixed version for vue-template-compiler.