GHSA-2pgj-5cv2-6xxw: FuelVM is vulnerable to heap memory allocation re-use bug
A memory safety vulnerability was present in the Fuel Virtual Machine (FuelVM), where memory reads could bypass expected access controls. Specifically, when a smart contract performed a mload (or other opcodes which access memory) on memory that had been deallocated using ret, it was still able to access the old memory contents. This occurred because the memory region was not zeroed out or otherwise marked as invalid. As a result, smart contracts could potentially read sensitive data left over from other contracts if the same memory was reallocated, violating isolation guarantees between contracts and enabling unintended data leakage.
All users running affected versions of FuelVM that relied on strict memory isolation between smart contracts were impacted.
References
Code Behaviors & Features
Detect and mitigate GHSA-2pgj-5cv2-6xxw with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →