Improper regular expression in Vue's parseHTML function leads to a potential regular expression denial of service vulnerability.
euvd · EUVD-2024-2953 · Published
No access to your tenant or devices. Every item links to its source. What this means
Improper regular expression in Vue's parseHTML function leads to a potential regular expression denial of service vulnerability.
Read the publisher's advisoryImproper regular expression in Vue's parseHTML function leads to a potential regular expression denial of service vulnerability.
Read the publisher's advisoryImproper regular expression in Vue's parseHTML function leads to a potential regular expression denial of service vulnerability.
Read the publisher's advisoryThe ReDoS can be exploited through the `parseHTML` function in the `html-parser.ts` file. This flaw allows attackers to slow down the application by providing specially crafted input that causes inefficient processing of regular expressions, leading to excessive resource consumption. To demonstrate this vulnerability, here's an example. In a Vue client-side application, create a new Vue instance with a template string that includes a `<script>` tag but closes it incorrectly with something like `</textarea>`. ```javascript new Vue({ el: '#app', template: ' <div> Hello, world! <script>${'<'.repeat(1000000)}</textarea> </div>' }); ``` Next, set up a basic HTML page (e.g., index.html) to load this JavaScript and mount the Vue instance: ```html <!DOCTYPE html> <html> <head> <title>My first Vue app</title> </head> <body> <div id=\"app\">Loading...</div> </body> </html> ``` When you visit the app in your browser at http://localhost:3000, you'll notice that the time taken to parse and mount the Vue application increases significantly due to the ReDoS vulnerability, demonstrating how the flaw can affect performance.
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2024-2953 · Published
euvd · EUVD-2024-2953 · Published
euvd · EUVD-2024-2953 · Published
euvd · EUVD-2024-2953 · Published
euvd · EUVD-2024-2953 · Published
euvd · EUVD-2024-2953 · Published
euvd · EUVD-2024-2953 · Published
euvd · EUVD-2024-2953 · Published
euvd · EUVD-2024-2953 · Published
euvd · EUVD-2024-2953 · Published
nvd · CVE-2024-9506 · Published
osv · GHSA-5j4c-8p2g-v4jx · Published
cve-program · CVE-2024-9506 · Published