p PatchFirst

PatchFirst · Свежие уязвимости

Уязвимости @openzeppelin/contracts-upgradeable · Страница 2

За последние 30 дней в @openzeppelin/contracts-upgradeable опубликовано уязвимостей: 0; в каталоге KEV: 0.

RSS ↗ JSON ↗
Фильтры уязвимостей
Сбросить фильтры

Уязвимостей: 22

  1. GHSA-q4h9-46xg-m3x9

    Без оценкиЕсть исправление

    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
    • Обновитесь до 4.3.2
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

  2. CVE-2021-39168

    Критический · CVSS 10EPSS 1,59%Есть исправление

    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
    • Обновитесь до 3.4.2
    • Обновитесь до 4.3.1
    Опубликовано Обновлено
    Исходное сообщение 1 ↗Исходное сообщение 2 ↗Исходное сообщение 3 ↗

Проверьте свой сервер

Сопоставьте установленный стек и версии со свежими базами уязвимостей.

Проверьте свой сервер →