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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@openzeppelin/contracts (source)	4.9.3 → 4.9.6

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)

v4.9.5

Compare Source

• Multicall: Make aware of non-canonical context (i.e. msg.sender is not _msgSender()), allowing compatibility with ERC2771Context. Patch duplicated Address.functionDelegateCall in v4.9.4 (removed).

v4.9.4

Compare Source

• ERC2771Context and Context: Introduce a _contextPrefixLength() getter, used to trim extra information appended to msg.data.
• Multicall: Make aware of non-canonical context (i.e. msg.sender is not _msgSender()), allowing compatibility with ERC2771Context.

---

Configuration

📅 Schedule: (in timezone Asia/Kolkata)

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

🚦 Automerge: Enabled.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sway	❌ Failed (Inspect)			Dec 8, 2024 10:39pm
sway-static	❌ Failed (Inspect)			Dec 8, 2024 10:39pm

[renovate]

⚠️ 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

/opt/containerbase/tools/corepack/0.34.6/16.14.0/node_modules/corepack/dist/lib/corepack.cjs:22598
  const isURL = URL.canParse(range);
                    ^

TypeError: URL.canParse is not a function
    at parseSpec (/opt/containerbase/tools/corepack/0.34.6/16.14.0/node_modules/corepack/dist/lib/corepack.cjs:22598:21)
    at Object.getSpec (/opt/containerbase/tools/corepack/0.34.6/16.14.0/node_modules/corepack/dist/lib/corepack.cjs:22747:55)
    at Engine.findProjectSpec (/opt/containerbase/tools/corepack/0.34.6/16.14.0/node_modules/corepack/dist/lib/corepack.cjs:22965:31)
    at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.34.6/16.14.0/node_modules/corepack/dist/lib/corepack.cjs:23004:24)
    at async Object.runMain (/opt/containerbase/tools/corepack/0.34.6/16.14.0/node_modules/corepack/dist/lib/corepack.cjs:23710:7)