Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency @openzeppelin/contracts to v4.9.6 [security] #78

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 23, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@openzeppelin/contracts (source) 4.9.5 -> 4.9.6 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2024-27094

Impact

The Base64.encode function encodes a bytes input by iterating over it in chunks of 3 bytes. When this input is not a multiple of 3, the last iteration may read parts of the memory that are beyond the input buffer.

Although the encode function pads the output for these cases, up to 4 bits of data are kept between the encoding and padding, corrupting the output if these bits were dirty (i.e. memory after the input is not 0). These conditions are more frequent in the following scenarios:

  • A bytes memory struct is allocated just after the input and the first bytes of it are non-zero.
  • The memory pointer is set to a non-empty memory location before allocating the input.

Developers should evaluate whether the extra bits can be maliciously manipulated by an attacker.

Patches

Upgrade to 5.0.2 or 4.9.6.

References

This issue was reported by the Independent Security Researcher Riley Holterhus through Immunefi (@​rileyholterhus on X)


Release Notes

OpenZeppelin/openzeppelin-contracts (@​openzeppelin/contracts)

v4.9.6

Compare Source

  • Base64: Fix issue where dirty memory located just after the input buffer is affecting the result. (#​4929)

Configuration

📅 Schedule: Branch creation - "" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 requested a review from a team as a code owner September 23, 2024 15:35
Copy link

github-actions bot commented Sep 23, 2024

Visit the preview URL for this PR (updated for commit f1c0fbf):

https://community-cookbook-staging--pr78-renovate-npm-openzep-fapolpdw.web.app

(expires Fri, 13 Dec 2024 13:59:27 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 1b876338aafcf55b4a02f1877984e116731756b1

@renovate renovate bot force-pushed the renovate/npm-openzeppelin-contracts-vulnerability branch 8 times, most recently from 42a78f7 to dfb6689 Compare October 1, 2024 15:23
@renovate renovate bot force-pushed the renovate/npm-openzeppelin-contracts-vulnerability branch 2 times, most recently from 14f65a3 to 4ef9c14 Compare October 7, 2024 16:43
@renovate renovate bot changed the title chore(deps): update devdependency @openzeppelin/contracts to v4.9.6 [security] chore(deps): update dependency @openzeppelin/contracts to v4.9.6 [security] Oct 7, 2024
@renovate renovate bot force-pushed the renovate/npm-openzeppelin-contracts-vulnerability branch 2 times, most recently from 7e2cfe2 to 8373b1d Compare October 16, 2024 21:13
@renovate renovate bot force-pushed the renovate/npm-openzeppelin-contracts-vulnerability branch 2 times, most recently from 13f6997 to 9998e0f Compare November 19, 2024 21:29
@renovate renovate bot force-pushed the renovate/npm-openzeppelin-contracts-vulnerability branch from 9998e0f to 0547ec3 Compare November 25, 2024 15:36
@renovate renovate bot force-pushed the renovate/npm-openzeppelin-contracts-vulnerability branch from 0547ec3 to f1c0fbf Compare December 6, 2024 13:57
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