@openzeppelin/contracts@4.3.0 vulnerabilities
Secure Smart Contract library for Solidity
-
latest version
5.0.0
-
latest non vulnerable version
-
first published
4 years ago
-
latest version published
2 months ago
-
licenses detected
- >=0
Direct Vulnerabilities
Known vulnerabilities in the @openzeppelin/contracts package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Improper Encoding or Escaping of Output. Contracts using Note: This can lead to unintended consequences or incorrect behavior in smart contracts that rely on the accurate identification of the sender. How to fix Improper Encoding or Escaping of Output? Upgrade |
>=4.0.0 <4.9.3
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Missing Authorization. By frontrunning the creation of a proposal, an attacker can become the proposer and gain the ability to cancel it. The attacker can do this repeatedly to try to prevent a proposal from being proposed at all. Note: In order for this attack to succeed, an attacker would need to have prior knowledge of a proposal creation. Impact: This issue impacts the How to fix Missing Authorization? Upgrade |
>=4.3.0 <4.9.1
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Denial of Service (DoS) such that a function in the implementation contract may be inaccessible if its selector clashes with one of the proxy's own selectors. Specifically, if the clashing function has a different signature with incompatible ABI encoding, the proxy could revert while attempting to decode the arguments from calldata. How to fix Denial of Service (DoS)? Upgrade |
>=3.2.0 <4.8.3
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Improper Input Validation due to missing signatures length validation of the proposal creation entry point ( How to fix Improper Input Validation? Upgrade |
>=4.3.0 <4.8.3
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature via How to fix Improper Verification of Cryptographic Signature? Upgrade |
<4.7.3
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Denial of Service (DoS) in the How to fix Denial of Service (DoS)? Upgrade |
>=2.3.0 <4.7.2
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Incorrect Calculation via the How to fix Incorrect Calculation? Upgrade |
>=4.3.0 <4.7.2
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Information Exposure. The contracts that may be affected are those that use How to fix Information Exposure? Upgrade |
>=4.1.0 <4.7.1
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Information Exposure. The contracts that may be affected are those that use How to fix Information Exposure? Upgrade |
>=4.0.0 <4.7.1
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Function Call With Incorrect Argument. The How to fix Function Call With Incorrect Argument? Upgrade |
>=4.3.0 <4.4.2
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Deserialization of Untrusted Data. It is possible for NOTE: This vulnerability has also been identified as: CVE-2021-46320 How to fix Deserialization of Untrusted Data? Upgrade |
>=3.2.0 <4.4.1
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Deserialization of Untrusted Data. It is possible for NOTE: This vulnerability has also been identified as: CVE-2022-39384 How to fix Deserialization of Untrusted Data? Upgrade |
>=3.2.0 <4.4.1
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Numeric Errors. When How to fix Numeric Errors? Upgrade |
>=4.2.0 <4.3.3
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Improper Initialization via uninitialized implementation contracts using How to fix Improper Initialization? Upgrade |
>=4.1.0 <4.3.2
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Improper Input Validation. Upgradeable contracts using Due to this vulnerability, it is recommended that all projects using the UUPS proxy pattern should How to fix Improper Input Validation? Upgrade |
>=4.1.0 <4.3.2
|
@openzeppelin/contracts is a library for contract development. Affected versions of this package are vulnerable to Privilege Escalation. A vulnerability in TimelockController allowed an actor with the executor role to escalate privileges. As a workaround, revoke the executor role from accounts not strictly under the team's control. It is recommended to revoke all executors that are not also proposers. When applying this mitigation, ensure there is at least one proposer and executor remaining. How to fix Privilege Escalation? Upgrade |
>=4.0.0-beta.0 <4.3.1
<3.4.2
|