Skip to content

OpenZeppelin Contracts vulnerable to Improper Escaping of Output

Moderate severity GitHub Reviewed Published Aug 10, 2023 in OpenZeppelin/openzeppelin-contracts • Updated Nov 4, 2023

Package

npm @openzeppelin/contracts (npm)

Affected versions

>= 4.0.0, < 4.9.3

Patched versions

4.9.3
npm @openzeppelin/contracts-upgradeable (npm)
>= 4.0.0, < 4.9.3
4.9.3

Description

Impact

OpenZeppelin Contracts is a library for secure smart contract development. Starting in version 4.0.0 and prior to version 4.9.3, contracts using ERC2771Context along with a custom trusted forwarder may see _msgSender return address(0) in calls that originate from the forwarder with calldata shorter than 20 bytes. This combination of circumstances does not appear to be common, in particular it is not the case for MinimalForwarder from OpenZeppelin Contracts, or any deployed forwarder the team is aware of, given that the signer address is appended to all calls that originate from these forwarders.

Patches

The problem has been patched in v4.9.3.

References

@frangio frangio published to OpenZeppelin/openzeppelin-contracts Aug 10, 2023
Published by the National Vulnerability Database Aug 10, 2023
Published to the GitHub Advisory Database Aug 11, 2023
Reviewed Aug 11, 2023
Last updated Nov 4, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.108%
(45th percentile)

Weaknesses

CVE ID

CVE-2023-40014

GHSA ID

GHSA-g4vp-m682-qqmp

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.