-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): bump vue from 2.7.16 to v3 (stable4.1) #10520
Open
renovate
wants to merge
1
commit into
stable4.1
Choose a base branch
from
renovate/stable4.1-npm-vue-vulnerability
base: stable4.1
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
bot
requested review from
ChristophWurst,
GretaD and
kesselb
as code owners
December 19, 2024 00:05
|
renovate
bot
changed the title
fix(deps): bump vue from 2.7.16 to v3 (stable4.1)
fix(deps): bump vue from 2.7.16 to v3 (stable4.1) - autoclosed
Jan 30, 2025
renovate
bot
changed the title
fix(deps): bump vue from 2.7.16 to v3 (stable4.1) - autoclosed
fix(deps): bump vue from 2.7.16 to v3 (stable4.1)
Jan 31, 2025
renovate
bot
force-pushed
the
renovate/stable4.1-npm-vue-vulnerability
branch
from
January 31, 2025 02:15
aef5a30
to
cde4bb1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.7.16
->^3.0.0-alpha
GitHub Vulnerability Alerts
CVE-2024-9506
The ReDoS can be exploited through the
parseHTML
function in thehtml-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>
.Next, set up a basic HTML page (e.g., index.html) to load this JavaScript and mount the Vue instance:
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.
ReDoS vulnerability in vue package that is exploitable through inefficient regex evaluation in the parseHTML function
CVE-2024-9506 / GHSA-5j4c-8p2g-v4jx
More information
Details
The ReDoS can be exploited through the
parseHTML
function in thehtml-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>
.Next, set up a basic HTML page (e.g., index.html) to load this JavaScript and mount the Vue instance:
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.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
References
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Configuration
📅 Schedule: Branch creation - "before 7am every weekday" in timezone Europe/Vienna, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.