Skip to content

Update dependency async to v3.2.2 [SECURITY] - #893

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-async-vulnerability
Open

Update dependency async to v3.2.2 [SECURITY]#893
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-async-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Jun 24, 2022

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
async (source) 3.2.03.2.2 age confidence

Prototype Pollution in async

CVE-2021-43138 / GHSA-fwr7-v2mv-hh25

More information

Details

A vulnerability exists in Async through 3.2.1 for 3.x and through 2.6.3 for 2.x (fixed in 3.2.2 and 2.6.4), which could let a malicious user obtain privileges via the mapValues() method.

Severity

  • CVSS Score: 7.8 / 10 (High)
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

caolan/async (async)

v3.2.2

Compare Source

  • Fix potential prototype pollution exploit

v3.2.1

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Jun 24, 2022

Copy link
Copy Markdown
Contributor Author

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock
This script must be run as root

@renovate renovate Bot changed the title Update dependency async to v3.2.2 [SECURITY] Update dependency async to v3.2.2 [SECURITY] - autoclosed Apr 3, 2024
@renovate renovate Bot closed this Apr 3, 2024
@renovate renovate Bot changed the title Update dependency async to v3.2.2 [SECURITY] - autoclosed Update dependency async to v3.2.2 [SECURITY] Apr 3, 2024
@renovate renovate Bot reopened this Apr 3, 2024
@renovate
renovate Bot force-pushed the renovate/npm-async-vulnerability branch from 7cb2d0a to f228fbf Compare January 23, 2025 18:14
@renovate renovate Bot changed the title Update dependency async to v3.2.2 [SECURITY] Update dependency async to v3.2.2 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-async-vulnerability branch March 27, 2026 02:02
@renovate renovate Bot changed the title Update dependency async to v3.2.2 [SECURITY] - autoclosed Update dependency async to v3.2.2 [SECURITY] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-async-vulnerability branch 2 times, most recently from f228fbf to afe0c56 Compare March 30, 2026 17:53
@renovate renovate Bot changed the title Update dependency async to v3.2.2 [SECURITY] Update dependency async to v3.2.2 [SECURITY] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title Update dependency async to v3.2.2 [SECURITY] - autoclosed Update dependency async to v3.2.2 [SECURITY] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/npm-async-vulnerability branch 2 times, most recently from afe0c56 to 6311c7d Compare April 27, 2026 21:27
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.

0 participants