Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade next from 10.2.3 to 12.0.9 #26

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

Conversation

Qdigital
Copy link
Owner

@Qdigital Qdigital commented Aug 1, 2022

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json
    • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
SNYK-JS-NODEFETCH-2964180
Yes Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages
Package name: next The new version differs by 250 commits.
  • 07431d3 v12.0.9
  • c938e20 v12.0.9-canary.12
  • c385d1b REMOVE: duplicate key in docs/testing.md (#33681)
  • 9b98c5a chore(docs): update security headers specification (#33673)
  • 865a079 v12.0.9-canary.11
  • b5d4564 Revert "Relay Support in Rust Compiler" (#33699)
  • 5c6c385 Use relative path for example (#33565)
  • 65c63c9 v12.0.9-canary.10
  • b20eb99 Relay Support in Rust Compiler (#33240)
  • 99d4d6c Implement web server as the request handler for edge SSR (#33635)
  • f0e31ee feat(next-swc): Update swc (#33675)
  • d055fee Updated docs for getServerSideProps and getStaticProps return values (#33577)
  • 8d1c585 v12.0.9-canary.9
  • 72658c9 fix(errors/no-cache): `netlify-plugin-cache-nextjs` has been deprecated (#33629)
  • 7452c0b Add `lazyRoot` optional property to `next/image` component (#33290)
  • 9dd0399 feat(next-swc): Update swc (#33628)
  • eba64c2 Clarify `headers` config option description (#33484)
  • f60a480 v12.0.9-canary.8
  • c13d9a0 Update other instances of node-fetch (#33617)
  • e8c15e5 Ensure fetch polyfill is loaded in next-server (#33616)
  • 9a2d97c [examples] Add new Tailwind CSS Prettier plugin to example (#33614)
  • 562439d Update to latest version of turbo (#33613)
  • 3329ac6 v12.0.9-canary.7
  • c71465d Clarify `next/image` usage with `next export` based on feedback. (#33555)

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.


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

For more information:
馃 View latest project report

馃洜 Adjust project settings

馃摎 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

馃 Learn about vulnerability in an interactive lesson of Snyk Learn.

@@ -17,7 +17,7 @@
"marked": "^2.0.0",
"moment": "^2.29.1",
"moment-strftime": "^0.5.0",
"next": "^10.0.7",
"next": "^12.0.9",
Copy link

Choose a reason for hiding this comment

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

Critical Vulnerability:

pkg:npm/next@12.0.9

1 Critical, 0 Severe, 0 Moderate, 0 Unknown vulnerabilities have been found across 1 dependencies

Components
    pkg:npm/next@12.0.9
      CRITICAL Vulnerabilities (1)

        [CVE-2022-23646] CWE-451: User Interface (UI) Misrepresentation of Critical Information

        Next.js is a React framework. Starting with version 10.0.0 and prior to version 12.1.0, Next.js is vulnerable to User Interface (UI) Misrepresentation of Critical Information. In order to be affected, the next.config.js file must have an images.domains array assigned and the image host assigned in images.domains must allow user-provided SVG. If the next.config.js file has images.loader assigned to something other than default, the instance is not affected. Version 12.1.0 contains a patch for this issue. As a workaround, change next.config.js to use a different loader configuration other than the default.

        CVSS Score: 7.5

        CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

        CWE: CWE-451


Reply with "@sonatype-lift help" for info about LiftBot commands.
Reply with "@sonatype-lift ignore" to tell LiftBot to leave out the above finding from this PR.
Reply with "@sonatype-lift ignoreall" to tell LiftBot to leave out all the findings from this PR and from the status bar in Github.

When talking to LiftBot, you need to refresh the page to see its response. Click here to get to know more about LiftBot commands.


Was this a good recommendation?
[ 馃檨 Not relevant ] - [ 馃槙 Won't fix ] - [ 馃槕 Not critical, will fix ] - [ 馃檪 Critical, will fix ] - [ 馃槉 Critical, fixing now ]

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.

None yet

2 participants