[Snyk] Security upgrade electron-packager from 9.0.1 to 14.0.0

[harunpehlivan]

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:
  • packages/electron/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	461/1000 Why? Recently disclosed, Has a fix available, CVSS 3.5	Regular Expression Denial of Service (ReDoS) SNYK-JS-DEBUG-3227433	Yes	No Known Exploit

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

Commit messages

Package name: electron-packager

The new version differs by 229 commits.

• 8d03dd7 14.0.0
• fe05b3e Merge pull request Difference in name vs displayName between Mac and Linux cypress-io/cypress#1017 from electron-userland/v14-develop
• a77eb2d chore: add NEWS entries for v14
• f8a3cac Linux/ia32 warning moved from Packager to @ electron/get (clicking on an openlayers canvas doesn't trigger any events cypress-io/cypress#1016)
• 67e3021 test: fix CLI test names, add --no-download.rejectUnauthorized test
• 5f09eb5 refactor: use object shorthand in targets exports
• cf7c725 feat: convert from electron-download to @ electron/get (.clear() on an input at maxlength doesn’t work  cypress-io/cypress#1002)
• cc470ef refactor: always test against post-1.0 versions of Electron (Add option to run specs outside of cypress directory cypress-io/cypress#1012)
• 51cce5b chore: install Wine via homebrew on macOS
• 6075368 chore: use yarn on Travis/macOS
• f56c84e chore: upgrade the ava ecosystem to ^2
• 2f6e385 chore: refactor codesign testing (Typings: fix Cypress interface cypress-io/cypress#1010)
• 8356c07 chore: avoid running npm install for fixtures (.contains() only yields first match cypress-io/cypress#1009)
• 99e28bb feat: ignore system junk files by default (Provide mechanism to skip binary download/install during "npm install" cypress-io/cypress#1005)
• 058f8d4 chore: upgrade electron-notarize to ^0.1.1
• 14625fb chore: upgrade rcedit to ^2.0.0 (Upgrade "debug" dep to version 2.6.9 or greater cypress-io/cypress#1003)
• c3a499a Replace extract-zip with cross-zip (After type, framework's internal state doesn't have time to update cypress-io/cypress#984)
• 481937a Wrap await example in a function because top-level await doesn't exist yet
• ae73870 chore: upgrade eslint-plugin-node to ^9.0.1
• 3be181a chore: split up NPM scripts
• 70b96d0 Upgrade asar to ^2.0.1
• 34a305a Update asar to ^2.0.0
• dd0f0de Drop mz for util.promisify (Wrong result in assertion be.visible in elements inside an SVG (Electron) cypress-io/cypress#983)
• b0b253b Update tempy requirement from ^0.2.1 to ^0.3.0 (If running single spec, name output video file using spec name cypress-io/cypress#980)

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:

🦉 Regular Expression Denial of Service (ReDoS)

[secure-code-warrior-for-github]

Micro-Learning Topic: Regular expression denial of service (Detected by phrase)

Matched on "Regular Expression Denial of Service"

What is this? (2min video)

Denial of Service (DoS) attacks caused by Regular Expression which causes the system to hang or cause them to work very slowly when attacker sends a well-crafted input(exponentially related to input size).Denial of service attacks significantly degrade the service quality experienced by legitimate users. These attacks introduce large response delays, excessive losses, and service interruptions, resulting in direct impact on availability.

Try a challenge in Secure Code Warrior

Micro-Learning Topic: Denial of service (Detected by phrase)

Matched on "Denial of Service"

The Denial of Service (DoS) attack is focused on making a resource (site, application, server) unavailable for the purpose it was designed. There are many ways to make a service unavailable for legitimate users by manipulating network packets, programming, logical, or resources handling vulnerabilities, among others. Source: https://www.owasp.org/index.php/Denial_of_Service

Try a challenge in Secure Code Warrior

[secureflag-knowledge-base]

Open Redirect

Play Labs on this vulnerability with SecureFlag!

Start Open Redirect Lab

Description

Open Redirects, otherwise known as Unvalidated Redirects and Forwards, are a class of vulnerability made possible when a web application, comprised of insufficient input-validation controls, is manipulated into redirecting unwitting users of the application to a malicious, attacker-controlled URL.

This type of exploit is popular with criminals involved in phishing and credential theft, unsurprising given the false layer of trust attributed to the fact that the modified link and the original site share the same server name.

Read more

Impact

There are many overlapping techniques criminals employ to dupe unwitting victims into handing over their hard-earned cash. One of these methods is undoubtedly betting on the misplaced trust many of us place in familiar server names. This write-up exemplifies how even the most arguably well-known URL of all, https://www.google.com, can be taken advantage of via its redirection facility.

In addition, Open Redirect vulnerabilities can:

• Lead to Cross-Site Scripting (XSS) attacks if the redirect uses data: or javascript: protocols;
• Potentially circumvent Server-Side Request Forgery (SSRF) filters;
• Nullify allow list effectiveness in some cases to bypass Content Security Policy (CSP);
• Lead to Carriage Return and Line Feed (CRLF) attacks if line breaks are present in the destination parameter.

Scenarios

As outlined above, attackers often use this attack as it 'hijacks' the trust users place in a well-known URL.

Here's a topical example from 2021; if the target domain is www.covidvaccinations.com, an attacker might craft the following URL:

http://www.covidvaccinations.com/redirect.php?url=http://attackerwebsite.com

Attackers send links like the one above in phishing campaigns in the hopes that they will lure a victim into clicking on the link.

Prevention

The following measures can be applied to either eliminate or drastically reduce the potential for Open Redirect exploitation:

• If they aren't necessary, don't use redirects and forwards!
• In cases where they are required, do not allow the URL as user input for the destination;
• When user input is unavoidable, validate the supplied value, its appropriateness for the application, and ensure it is authorized for the user:
  • This can be a fiddly task, so closely adhere to best practices and ensure continued maintenance.
• If possible, force the user to provide an ID or token that is mapped server-side to a complete target URL;
• Input sanitization should be implemented by creating an allow list of trusted URLs determined by host or regex.

Testing

Verify that URL redirects and forwards only allow destinations which appear on an allow list, or show a warning when redirecting to potentially untrusted content.

• OWASP ASVS: 5.1.5

View this in the SecureFlag Knowledge Base

[secure-code-warrior-for-github]

Micro-Learning Topic: Cross-site scripting (Detected by phrase)

Matched on "Cross-Site Scripting"

What is this? (2min video)

Cross-site scripting vulnerabilities occur when unescaped input is rendered into a page displayed to the user. When HTML or script is included in the input, it will be processed by a user's browser as HTML or script and can alter the appearance of the page or execute malicious scripts in their user context.

Try a challenge in Secure Code Warrior

Helpful references

• Prevent Cross-Site Scripting (XSS) in ASP.NET Core - A detailed Microsoft article on how to prevent cross-site scripting in ASP.NET Core.
• OWASP Cross Site Scripting (XSS) Software Attack - OWASP community page with comprehensive information about cross site scripting, and links to various OWASP resources to help detect or prevent it.
• OWASP Cross Site Scripting Prevention Cheat Sheet - This article provides a simple positive model for preventing XSS using output encoding properly.

Micro-Learning Topic: Open redirect (Detected by phrase)

Matched on "Open Redirect"

What is this? (2min video)

This vulnerability refers to the ability of an attacker to arbitrarily perform a redirection (external) or forward (internal) against the system. It arises due to insufficient validation or sanitisation of inputs used to perform a redirect or forward and may result in privilege escalation (in the case of a forward) or may be used to launch phishing attacks against users (in the case of redirects).

Try a challenge in Secure Code Warrior

Helpful references

• OWASP Unvalidated Redirects and Forwards Cheat Sheet - This cheatsheet is focused on providing clear, simple, actionable guidance for preventing redirection and forwarding flaws in your applications.
• Preventing Open Redirection Attacks (C#) - A detailed Microsoft article on how to prevent open redirection vulnerabilities in ASP.NET MVC.

Micro-Learning Topic: Server-side request forgery (Detected by phrase)

Matched on "Server-Side Request Forgery"

What is this? (2min video)

Server-Side Request Forgery (SSRF) vulnerabilities are caused when an attacker can supply or modify a URL that reads or sends data to the server. The attacker can create a malicious request with a manipulated URL, when this request reaches the server, the server-side code executes the exploit URL causing the attacker to be able to read data from services that shouldn't be exposed.

Try a challenge in Secure Code Warrior

Micro-Learning Topic: Unvalidated redirect (Detected by phrase)

Matched on "Unvalidated Redirect"

What is this? (2min video)

This vulnerability refers to the ability of an attacker to arbitrarily perform a redirection (external) or forward (internal) against the system. It arises due to insufficient validation or sanitisation of inputs used to perform a redirect or forward and may result in privilege escalation (in the case of a forward) or may be used to launch phishing attacks against users (in the case of redirects).

Try a challenge in Secure Code Warrior

Helpful references

• OWASP Unvalidated Redirects and Forwards Cheat Sheet - This cheatsheet is focused on providing clear, simple, actionable guidance for preventing redirection and forwarding flaws in your applications.
• Preventing Open Redirection Attacks (C#) - A detailed Microsoft article on how to prevent open redirection vulnerabilities in ASP.NET MVC.