starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[PR #607] [MERGED] Bump node-forge from 0.9.1 to 0.10.0 in /docs #3271

New issue

Closed

opened 2026-02-26 07:38:41 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 07:38:41 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/NginxProxyManager/nginx-proxy-manager/pull/607
Author: @dependabot[bot]
Created: 9/17/2020
Status: ✅ Merged
Merged: 10/14/2020
Merged by: @jc21

Base: develop ← Head: dependabot/npm_and_yarn/docs/node-forge-0.10.0

📝 Commits (2)

28f7208 Merge pull request #592 from jc21/develop
e5cb750 Bump node-forge from 0.9.1 to 0.10.0 in /docs

📊 Changes

2 files changed (+5 additions, -5 deletions)

View changed files

📝 docs/package.json (+1 -1)
📝 docs/yarn.lock (+4 -4)

📄 Description

Bumps node-forge from 0.9.1 to 0.10.0.

Changelog

Sourced from node-forge's changelog.

0.10.0 - 2020-09-01

Changed

BREAKING: Node.js 4 no longer supported. The code may still work, and non-invasive patches to keep it working will be considered. However, more modern tools no longer support old Node.js versions making testing difficult.

Removed

BREAKING: Remove util.getPath, util.setPath, and util.deletePath. util.setPath had a potential prototype pollution security issue when used with unsafe inputs. These functions are not used by forge itself. They date from an early time when forge was targeted at providing general helper functions. The library direction changed to be more focused on cryptography. Many other excellent libraries are more suitable for general utilities. If you need a replacement for these functions, consier get, set, and unset from lodash. But also consider the potential similar security issues with those APIs.

0.9.2 - 2020-09-01

Changed

Added util.setPath security note to function docs and to README.

Notes

SECURITY: The util.setPath function has the potential to cause prototype pollution if used with unsafe input.

This function is not used internally by forge.

The rest of the library is unaffected by this issue.

Do not use unsafe input with this function.

Usage with known input should function as expected. (Including input intentionally using potentially problematic keys.)

No code changes will be made to address this issue in 0.9.x. The current behavior could be considered a feature rather than a security issue. 0.10.0 will be released that removes util.getPath and util.setPath. Consider get and set from lodash if you need replacements. But also consider the potential similar security issues with those APIs.

https://snyk.io/vuln/SNYK-JS-NODEFORGE-598677

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7720

Commits

8018c3e Release 0.10.0.
6a1e3ef Remove object path functions.
30d560c Remove Node.js 4 support.
1ba83ec Update dependencies.
81abd87 Improve linting.
7b59028 Test on Node.js 14.
ba13a1c Update webpack.
c8d5395 Add travis browser test names.
afc5a72 Update dependencies.
ba0207f Test on Node.js 12.
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
@dependabot use these labels will set the current labels as the default for future PRs for this repo and language
@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/NginxProxyManager/nginx-proxy-manager/pull/607 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 9/17/2020 **Status:** ✅ Merged **Merged:** 10/14/2020 **Merged by:** [@jc21](https://github.com/jc21) **Base:** `develop` ← **Head:** `dependabot/npm_and_yarn/docs/node-forge-0.10.0` --- ### 📝 Commits (2) - [`28f7208`](https://github.com/NginxProxyManager/nginx-proxy-manager/commit/28f72086ec2d8cd168fbf1aab99c770dfdc0f092) Merge pull request #592 from jc21/develop - [`e5cb750`](https://github.com/NginxProxyManager/nginx-proxy-manager/commit/e5cb7500153756a8e30323da0245c63fe1420cd2) Bump node-forge from 0.9.1 to 0.10.0 in /docs ### 📊 Changes **2 files changed** (+5 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `docs/package.json` (+1 -1) 📝 `docs/yarn.lock` (+4 -4) </details> ### 📄 Description Bumps [node-forge](https://github.com/digitalbazaar/forge) from 0.9.1 to 0.10.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/digitalbazaar/forge/blob/master/CHANGELOG.md">node-forge's changelog</a>.</em></p> <blockquote> <h2>0.10.0 - 2020-09-01</h2> <h3>Changed</h3> <ul> <li><strong>BREAKING</strong>: Node.js 4 no longer supported. The code <em>may</em> still work, and non-invasive patches to keep it working will be considered. However, more modern tools no longer support old Node.js versions making testing difficult.</li> </ul> <h3>Removed</h3> <ul> <li><strong>BREAKING</strong>: Remove <code>util.getPath</code>, <code>util.setPath</code>, and <code>util.deletePath</code>. <code>util.setPath</code> had a potential prototype pollution security issue when used with unsafe inputs. These functions are not used by <code>forge</code> itself. They date from an early time when <code>forge</code> was targeted at providing general helper functions. The library direction changed to be more focused on cryptography. Many other excellent libraries are more suitable for general utilities. If you need a replacement for these functions, consier <code>get</code>, <code>set</code>, and <code>unset</code> from <a href="https://lodash.com/">lodash</a>. But also consider the potential similar security issues with those APIs.</li> </ul> <h2>0.9.2 - 2020-09-01</h2> <h3>Changed</h3> <ul> <li>Added <code>util.setPath</code> security note to function docs and to README.</li> </ul> <h3>Notes</h3> <ul> <li><strong>SECURITY</strong>: The <code>util.setPath</code> function has the potential to cause prototype pollution if used with unsafe input. <ul> <li>This function is <strong>not</strong> used internally by <code>forge</code>.</li> <li>The rest of the library is unaffected by this issue.</li> <li><strong>Do not</strong> use unsafe input with this function.</li> <li>Usage with known input should function as expected. (Including input intentionally using potentially problematic keys.)</li> <li>No code changes will be made to address this issue in 0.9.x. The current behavior <em>could</em> be considered a feature rather than a security issue. 0.10.0 will be released that removes <code>util.getPath</code> and <code>util.setPath</code>. Consider <code>get</code> and <code>set</code> from <a href="https://lodash.com/">lodash</a> if you need replacements. But also consider the potential similar security issues with those APIs.</li> <li><a href="https://snyk.io/vuln/SNYK-JS-NODEFORGE-598677">https://snyk.io/vuln/SNYK-JS-NODEFORGE-598677</a></li> <li><a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7720">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7720</a></li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/digitalbazaar/forge/commit/8018c3ea6f8e75d2df1b9ce4ec9c536db3db37e6"><code>8018c3e</code></a> Release 0.10.0.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/6a1e3ef74f6eb345bcff1b82184201d1e28b6756"><code>6a1e3ef</code></a> Remove object path functions.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/30d560c6b522b9a97a67d9101ecf8f860a4ba63a"><code>30d560c</code></a> Remove Node.js 4 support.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/1ba83ecca436c2e1d0d37ea154467e9934019504"><code>1ba83ec</code></a> Update dependencies.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/81abd87a9a8ef705af17d1e712a086ef4b7869a1"><code>81abd87</code></a> Improve linting.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/7b59028142bb5f5e299df0d0931a8306d7d7046b"><code>7b59028</code></a> Test on Node.js 14.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/ba13a1c8bfdb1d6abb286fa7fcb82a57b40ae345"><code>ba13a1c</code></a> Update webpack.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/c8d5395e078f838604eb9df32ef9d298288057fd"><code>c8d5395</code></a> Add travis browser test names.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/afc5a728f5c6bf5cb80eddb5b85c7340b28bfa51"><code>afc5a72</code></a> Update dependencies.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/ba0207fa359f79a5af0e71d12f488a846e9265f6"><code>ba0207f</code></a> Test on Node.js 12.</li> <li>Additional commits viewable in <a href="https://github.com/digitalbazaar/forge/compare/0.9.1...0.10.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=node-forge&package-manager=npm_and_yarn&previous-version=0.9.1&new-version=0.10.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/jc21/nginx-proxy-manager/network/alerts). </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-02-26 07:38:41 +03:00

closed this issue
added the
pull-request
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#3271

No description provided.

Rows
Columns