Skip to content

[Snyk] Upgrade @testing-library/jest-dom from 5.16.5 to 5.17.0 #380

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

nejidevelops
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade @testing-library/jest-dom from 5.16.5 to 5.17.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released 2 years ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-ANSIHTML-1296849
696 Proof of Concept
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-ANSIREGEX-1583908
696 Proof of Concept
high severity Denial of Service (DoS)
SNYK-JS-HTTPPROXYMIDDLEWARE-8229906
696 Proof of Concept
high severity Server-side Request Forgery (SSRF)
SNYK-JS-IP-6240864
696 Proof of Concept
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-SSRI-1246392
696 Proof of Concept
high severity Prototype Pollution
SNYK-JS-UNSETVALUE-2400660
696 No Known Exploit
high severity Prototype Pollution
SNYK-JS-MERGE-1040469
696 No Known Exploit
high severity Prototype Pollution
SNYK-JS-MERGE-1042987
696 Proof of Concept
high severity Inefficient Regular Expression Complexity
SNYK-JS-MICROMATCH-6838728
696 No Known Exploit
high severity Inefficient Regular Expression Complexity
SNYK-JS-MICROMATCH-6838728
696 No Known Exploit
high severity Inefficient Regular Expression Complexity
SNYK-JS-MICROMATCH-6838728
696 No Known Exploit
high severity Excessive Platform Resource Consumption within a Loop
SNYK-JS-BRACES-6838727
696 Proof of Concept
high severity Excessive Platform Resource Consumption within a Loop
SNYK-JS-BRACES-6838727
696 Proof of Concept
high severity Excessive Platform Resource Consumption within a Loop
SNYK-JS-BRACES-6838727
696 Proof of Concept
high severity Improper Verification of Cryptographic Signature
SNYK-JS-BROWSERIFYSIGN-6037026
696 No Known Exploit
high severity Denial of Service (DoS)
SNYK-JS-WS-7266574
696 Proof of Concept
high severity Cross-site Scripting (XSS)
SNYK-JS-SERIALIZEJAVASCRIPT-536840
696 No Known Exploit
high severity Arbitrary Code Injection
SNYK-JS-SERIALIZEJAVASCRIPT-570062
696 Proof of Concept
high severity Cross-site Scripting (XSS)
SNYK-JS-SERIALIZEJAVASCRIPT-6056521
696 No Known Exploit
high severity Remote Code Execution (RCE)
SNYK-JS-SHELLQUOTE-1766506
696 No Known Exploit
high severity Prototype Pollution
SNYK-JS-LOADERUTILS-3043105
696 No Known Exploit
high severity Code Injection
SNYK-JS-LODASHTEMPLATE-1088054
696 Proof of Concept
high severity Improper Verification of Cryptographic Signature
SNYK-JS-NODEFORGE-2430339
696 No Known Exploit
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-CROSSSPAWN-8303230
696 Proof of Concept
high severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-8172694
696 No Known Exploit
high severity Improper Handling of Extra Parameters
SNYK-JS-FOLLOWREDIRECTS-6141137
696 Proof of Concept
high severity Asymmetric Resource Consumption (Amplification)
SNYK-JS-BODYPARSER-7926860
696 No Known Exploit
high severity Path Traversal
SNYK-JS-WEBPACKDEVMIDDLEWARE-6476555
696 Proof of Concept
high severity Denial of Service (DoS)
SNYK-JS-WS-7266574
696 Proof of Concept
medium severity Server-Side Request Forgery (SSRF)
SNYK-JS-IP-7148531
696 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-TERSER-2806366
696 No Known Exploit
medium severity Prototype Pollution
SNYK-JS-TOUGHCOOKIE-5672873
696 Proof of Concept
medium severity Prototype Pollution
SNYK-JS-TOUGHCOOKIE-5672873
696 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-UGLIFYJS-1727251
696 No Known Exploit
medium severity Cross-site Scripting (XSS)
SNYK-JS-WEBPACK-7840298
696 Proof of Concept
medium severity Improper Verification of Cryptographic Signature
SNYK-JS-NODEFORGE-2430341
696 No Known Exploit
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PATHTOREGEXP-7925106
696 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PATHTOREGEXP-8482416
696 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-POSTCSS-1255640
696 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PROMPTS-1729737
696 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-MINIMATCH-3050818
696 No Known Exploit
medium severity Open Redirect
SNYK-JS-NODEFORGE-2330875
696 Proof of Concept
medium severity Prototype Pollution
SNYK-JS-NODEFORGE-2331908
696 No Known Exploit
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-BROWSERSLIST-1090194
696 Proof of Concept
medium severity Cross-site Scripting (XSS)
SNYK-JS-COOKIE-8163060
696 No Known Exploit
medium severity Prototype Pollution
SNYK-JS-YARGSPARSER-560381
696 Proof of Concept
medium severity Prototype Pollution
SNYK-JS-YARGSPARSER-560381
696 Proof of Concept
medium severity Denial of Service (DoS)
SNYK-JS-SOCKJS-575261
696 Proof of Concept
medium severity Reverse Tabnabbing
SNYK-JS-ISTANBULREPORTS-2328088
696 No Known Exploit
medium severity Prototype Pollution
SNYK-JS-JSON5-3182856
696 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-LOADERUTILS-3042992
696 No Known Exploit
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-LOADERUTILS-3105943
696 No Known Exploit
medium severity Improper Verification of Cryptographic Signature
SNYK-JS-NODEFORGE-2430337
696 No Known Exploit
low severity Regular Expression Denial of Service (ReDoS)
npm:braces:20180219
696 Proof of Concept
low severity Cross-site Scripting
SNYK-JS-SERVESTATIC-7926865
696 No Known Exploit
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577916
696 Proof of Concept
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577917
696 Proof of Concept
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577918
696 Proof of Concept
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-8187303
696 Proof of Concept
critical severity Information Exposure
SNYK-JS-ELLIPTIC-8720086
696 Proof of Concept
medium severity Open Redirect
SNYK-JS-EXPRESS-6474509
696 No Known Exploit
medium severity Cross-site Scripting
SNYK-JS-EXPRESS-7926867
696 No Known Exploit
medium severity Information Exposure
SNYK-JS-FOLLOWREDIRECTS-6444610
696 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-GLOBPARENT-1016905
696 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-HTMLMINIFIER-3091181
696 Proof of Concept
medium severity Command Injection
SNYK-JS-REACTDEVUTILS-1083268
696 Proof of Concept
medium severity Server-side Request Forgery (SSRF)
SNYK-JS-REQUEST-3361831
696 Proof of Concept
low severity Cross-site Scripting
SNYK-JS-SEND-7926862
696 No Known Exploit
critical severity Incomplete List of Disallowed Inputs
SNYK-JS-BABELTRAVERSE-5962462
696 Proof of Concept
critical severity Incomplete List of Disallowed Inputs
SNYK-JS-BABELTRAVERSE-5962463
696 Proof of Concept
low severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-WORDWRAP-3149973
696 Proof of Concept
Release notes
Package name: @testing-library/jest-dom from @testing-library/jest-dom GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @testing-library/jest-dom from 5.16.5 to 5.17.0.

See this package in npm:
@testing-library/jest-dom

See this project in Snyk:
https://app.snyk.io/org/newtonombese1/project/0dbeb3c7-0f2b-4df0-ac5a-fd0108caddf4?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @nejidevelops, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

Hello team, gemini-code-assist here to provide a summary of this pull request. This PR, automatically generated by Snyk, aims to upgrade the @testing-library/jest-dom dependency from version 5.16.5 to 5.17.0. The primary motivation for this upgrade is to address a significant number of security vulnerabilities identified in the current version and its transitive dependencies, including several high and critical severity issues related to ReDoS, Prototype Pollution, SSRF, DoS, XSS, and more. The upgrade itself is a minor version bump and the release notes indicate the addition of a new feature (toHaveAccessibleErrorMessage) and the deprecation of an older one (toHaveErrorMessage), alongside a bug fix in a previous version (5.16.5).

Highlights

  • Dependency Upgrade: Upgrades the @testing-library/jest-dom package from version 5.16.5 to 5.17.0.
  • Security Fixes: Addresses numerous security vulnerabilities reported by Snyk, including multiple high and critical severity issues across various underlying dependencies.
  • New Feature/Deprecation: The upgraded version 5.17.0 introduces a new matcher toHaveAccessibleErrorMessage and deprecates toHaveErrorMessage.

Changelog

  • 0x01-react_intro/task_3/dashboard/package.json
    • Updated the version of @testing-library/jest-dom in the dependencies section from ^5.16.4 to ^5.17.0.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


A package version, old and worn,
Security flaws, a digital thorn.
Upgrade it now, make tests bright,
With jest-dom fixed, all feels right.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request, automatically generated by Snyk, upgrades @testing-library/jest-dom from ^5.16.4 (likely resolved to 5.16.5 as per Snyk's description) to ^5.17.0. This is a valuable update as it addresses numerous security vulnerabilities, including several critical and high-severity ones, as detailed in the PR description.

The change itself is a straightforward version bump in the package.json file and appears correct. Thank you for addressing these security concerns!

Summary of Findings

  • Awareness of Deprecated Matcher: The release notes for @testing-library/[email protected] mention that the toHaveErrorMessage matcher has been deprecated in favor of a new toHaveAccessibleErrorMessage matcher. While this upgrade is a minor version bump and shouldn't introduce breaking changes to existing usage of toHaveErrorMessage, it would be good practice to update any instances of the deprecated matcher in your test suite to the new one when time permits. This is a low-severity item and not commented on directly due to review settings, but worth noting for future maintainability.
  • Lock File Update and Testing: After merging this change, remember to run npm install or yarn install to update your lock file (package-lock.json or yarn.lock) and install the new version of the dependency. Thorough testing of your application, particularly the parts covered by Jest tests, is recommended to ensure this upgrade doesn't introduce any unexpected behavior. This is a general best practice for dependency upgrades and is considered low severity, hence not commented directly due to review settings.

Merge Readiness

The pull request is highly recommended for merging as it addresses significant security vulnerabilities. The code change itself is minimal and correct. Before merging, the author should ensure that their local test suite passes after updating dependencies and regenerating the lock file. As I am an AI, I am not authorized to approve pull requests; please ensure appropriate human review and approval before merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants