github-starred/awesome-cryptography
2
0
Fork 0
mirror of https://github.com/sobolevn/awesome-cryptography.git synced 2026-03-12 01:54:54 -05:00
Code Issues 29 Packages Projects Releases Wiki Activity

[PR #117] [MERGED] [Security] Bump minimist from 1.2.0 to 1.2.5 #133

New Issue
Closed
opened 2025-11-06 09:10:02 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-06 09:10:02 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/sobolevn/awesome-cryptography/pull/117
Author: @dependabot-preview[bot]
Created: 7/6/2020
Status: ✅ Merged
Merged: 7/20/2020
Merged by: @sobolevn

Base: master ← Head: dependabot/npm_and_yarn/minimist-1.2.5

📝 Commits (1)

  • 6a26c1d [Security] Bump minimist from 1.2.0 to 1.2.5

📊 Changes

1 file changed (+1 additions, -5 deletions)

View changed files

📝 yarn.lock (+1 -5)

📄 Description

Bumps minimist from 1.2.0 to 1.2.5. This update includes security fixes.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

High severity vulnerability that affects minimist minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "proto" payload.

Affected versions: >= 1.0.0 < 1.2.3

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects acorn and minimist minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a "constructor" or "proto" payload.

Affected versions: < 1.2.2

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects acorn, minimist, and svjsl There are high severity security vulnerabilities in two of ESLints dependencies: - acorn - minimist

The releases 1.8.3 and lower of svjsl (JSLib-npm) are vulnerable, but only if installed in a developer environment. A patch has been released (v1.8.4) which fixes these vulnerabilities.

Identifiers:

  • CVE-2020-7598
  • SNYK-JS-ACORN-559469 (doesn&#39;t have a CVE identifier)

Affected versions: < 1.2.2

Commits

Dependabot compatibility score

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
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

🔄 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/sobolevn/awesome-cryptography/pull/117 **Author:** [@dependabot-preview[bot]](https://github.com/apps/dependabot-preview) **Created:** 7/6/2020 **Status:** ✅ Merged **Merged:** 7/20/2020 **Merged by:** [@sobolevn](https://github.com/sobolevn) **Base:** `master` ← **Head:** `dependabot/npm_and_yarn/minimist-1.2.5` --- ### 📝 Commits (1) - [`6a26c1d`](https://github.com/sobolevn/awesome-cryptography/commit/6a26c1dd9523af8e09d01bec5b24fc93f9e22b9d) [Security] Bump minimist from 1.2.0 to 1.2.5 ### 📊 Changes **1 file changed** (+1 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `yarn.lock` (+1 -5) </details> ### 📄 Description Bumps [minimist](https://github.com/substack/minimist) from 1.2.0 to 1.2.5. **This update includes security fixes.** <details> <summary>Vulnerabilities fixed</summary> <p><em>Sourced from <a href="https://github.com/advisories/GHSA-vh95-rmgr-6w4m">The GitHub Security Advisory Database</a>.</em></p> <blockquote> <p><strong>High severity vulnerability that affects minimist</strong> minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a &quot;constructor&quot; or &quot;<strong>proto</strong>&quot; payload.</p> <p>Affected versions: &gt;= 1.0.0 &lt; 1.2.3</p> </blockquote> <p><em>Sourced from <a href="https://github.com/advisories/GHSA-7fhm-mqm4-2wp7">The GitHub Security Advisory Database</a>.</em></p> <blockquote> <p><strong>Moderate severity vulnerability that affects acorn and minimist</strong> minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a &quot;constructor&quot; or &quot;<strong>proto</strong>&quot; payload.</p> <p>Affected versions: &lt; 1.2.2</p> </blockquote> <p><em>Sourced from <a href="https://github.com/advisories/GHSA-7fhm-mqm4-2wp7">The GitHub Security Advisory Database</a>.</em></p> <blockquote> <p><strong>Moderate severity vulnerability that affects acorn, minimist, and svjsl</strong> There are high severity security vulnerabilities in two of ESLints dependencies: - <a href="https://app.snyk.io/vuln/SNYK-JS-ACORN-559469">acorn</a> - <a href="https://app.snyk.io/vuln/SNYK-JS-MINIMIST-559764">minimist</a></p> <p>The releases 1.8.3 and lower of svjsl (JSLib-npm) are vulnerable, but only if installed in a developer environment. A patch has been released (v1.8.4) which fixes these vulnerabilities.</p> <p>Identifiers:</p> <ul> <li><a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7598">CVE-2020-7598</a></li> <li>SNYK-JS-ACORN-559469 (doesn&amp;#39;t have a CVE identifier)</li> </ul> <p>Affected versions: &lt; 1.2.2</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/substack/minimist/commit/aeb3e27dae0412de5c0494e9563a5f10c82cc7a9"><code>aeb3e27</code></a> 1.2.5</li> <li><a href="https://github.com/substack/minimist/commit/278677b171d956b46613a158c6c486c3ef979b20"><code>278677b</code></a> 1.2.4</li> <li><a href="https://github.com/substack/minimist/commit/4cf1354839cb972e38496d35e12f806eea92c11f"><code>4cf1354</code></a> security notice</li> <li><a href="https://github.com/substack/minimist/commit/1043d212c3caaf871966e710f52cfdf02f9eea4b"><code>1043d21</code></a> additional test for constructor prototype pollution</li> <li><a href="https://github.com/substack/minimist/commit/6457d7440a47f329c12c4a5abfbce211c4235b93"><code>6457d74</code></a> 1.2.3</li> <li><a href="https://github.com/substack/minimist/commit/38a4d1caead72ef99e824bb420a2528eec03d9ab"><code>38a4d1c</code></a> even more aggressive checks for protocol pollution</li> <li><a href="https://github.com/substack/minimist/commit/13c01a5327736903704984b7f65616b8476850cc"><code>13c01a5</code></a> more failing proto pollution tests</li> <li><a href="https://github.com/substack/minimist/commit/f34df077a6b2bee1344188849a95e66777109e89"><code>f34df07</code></a> 1.2.2</li> <li><a href="https://github.com/substack/minimist/commit/67d3722413448d00a62963d2d30c34656a92d7e2"><code>67d3722</code></a> cleanup</li> <li><a href="https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94"><code>63e7ed0</code></a> don't assign onto <strong>proto</strong></li> <li>Additional commits viewable in <a href="https://github.com/substack/minimist/compare/1.2.0...1.2.5">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=minimist&package-manager=npm_and_yarn&previous-version=1.2.0&new-version=1.2.5)](https://dependabot.com/compatibility-score/?dependency-name=minimist&package-manager=npm_and_yarn&previous-version=1.2.0&new-version=1.2.5) 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 - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-06 09:10:02 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
content-request
enhancement
foreign-invalid-link
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
section-request
waits-feedback
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-cryptography#133
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?