Skip to content
This repository has been archived by the owner on May 3, 2022. It is now read-only.

chore(deps): update dependency node-forge to 1.0.0 [security] #370

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 23, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change
node-forge 0.7.6 -> 1.0.0

GitHub Vulnerability Alerts

CVE-2020-7720

The package node-forge before 0.10.0 is vulnerable to Prototype Pollution via the util.setPath function. Note: Version 0.10.0 is a breaking change removing the vulnerable functions.

GHSA-gf8q-jrpm-jvxq

Impact

The regex used for the forge.util.parseUrl API would not properly parse certain inputs resulting in a parsed data structure that could lead to undesired behavior.

Patches

forge.util.parseUrl and other very old related URL APIs were removed in 1.0.0 in favor of letting applications use the more modern WHATWG URL Standard API.

Workarounds

Ensure code does not directly or indirectly call forge.util.parseUrl with untrusted input.

References

For more information

If you have any questions or comments about this advisory:

GHSA-wxgw-qj99-44c2

Impact

forge.util.setPath had a potential prototype pollution issue if called with untrusted keys. This API was not used by forge itself.

Patches

The forge.util.setPath API and related functions were removed in 0.10.0.

Workarounds

Don't call forge.util.setPath directly or indirectly with untrusted keys.

References

For more information

If you have any questions or comments about this advisory:

GHSA-5rrq-pxf6-6jx5

Impact

The forge.debug API had a potential prototype pollution issue if called with untrusted input. The API was only used for internal debug purposes in a safe way and never documented or advertised. It is suspected that uses of this API, if any exist, would likely not have used untrusted inputs in a vulnerable way.

Patches

The forge.debug API and related functions were removed in 1.0.0.

Workarounds

Don't use the forge.debug API directly or indirectly with untrusted input.

References

For more information

If you have any questions or comments about this advisory:

CVE-2022-0122

parseUrl functionality in node-forge mishandles certain uses of backslash such as https:///\ and interprets the URI as a relative path.


Configuration

📅 Schedule: "" in timezone Europe/Berlin.

🚦 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.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot requested review from dnsos and ff6347 as code owners November 23, 2021 05:30
@netlify
Copy link

netlify bot commented Nov 23, 2021

✔️ Deploy Preview for tsb-labsite ready!

🔨 Explore the source changes: 61b8493

🔍 Inspect the deploy log: https://app.netlify.com/sites/tsb-labsite/deploys/61dc5194806d760007eb5ed1

😎 Browse the preview: https://deploy-preview-370--tsb-labsite.netlify.app

@renovate renovate bot force-pushed the renovate/npm-node-forge-vulnerability branch 2 times, most recently from 77c31e1 to 8da5502 Compare January 5, 2022 13:31
@renovate renovate bot force-pushed the renovate/npm-node-forge-vulnerability branch from 8da5502 to 61b8493 Compare January 10, 2022 15:32
@renovate renovate bot changed the title chore(deps): update dependency node-forge to 0.10.0 [security] chore(deps): update dependency node-forge to 1.0.0 [security] Jan 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant