p PatchFirst

PatchFirst · Latest vulnerabilities

@openzeppelin/contracts-upgradeable vulnerabilities · Page 2

Vulnerabilities published for @openzeppelin/contracts-upgradeable in the last 30 days: 0. Listed in the KEV catalogue: 0.

RSS ↗ JSON ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 22

  1. GHSA-q4h9-46xg-m3x9

    Not ratedFix available

    UUPSUpgradeable vulnerability in @openzeppelin/contracts-upgradeable

    ### Impact Upgradeable contracts using `UUPSUpgradeable` may be vulnerable to an attack affecting uninitialized implementation contracts. We will update this advisory with more information soon. ### Patches A fix is included in version 4.3.2 of `@openzeppelin/contracts` and `@openzeppelin/contracts-upgradeable`. ### Workarounds Initialize implementation contracts using `UUPSUpgradeable` by invoking the initializer function (usually called `initialize`). An example is provided [in the forum](https://forum.openzeppelin.com/t/security-advisory-initialize-uups-implementation-contracts/15301). ### References A post-mortem will be published

    @openzeppelin/contracts-upgradeableNode.js
    • Update to 4.3.2
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

  2. CVE-2021-39168

    Critical · CVSS 10EPSS 1.59%Fix available

    TimelockController vulnerability in OpenZeppelin Contracts

    OpenZepplin is a library for smart contract development. In affected versions a vulnerability in TimelockController allowed an actor with the executor role to escalate privileges. Further details about the vulnerability will be disclosed at a later date. As a workaround revoke the executor role from accounts not strictly under the team's control. We recommend revoking all executors that are not also proposers. When applying this mitigation, ensure there is at least one proposer and executor remaining.

    @openzeppelin/contracts-upgradeable @openzeppelin/contracts-upgradeableNode.js
    • Update to 3.4.2
    • Update to 4.3.1
    Published Updated
    Source advisory 1 ↗Source advisory 2 ↗Source advisory 3 ↗

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →