Critical · published September 24, 2022
🔥 A sneaky miscalculation in gas management can lead to consensus chaos! This bug in Besu affects versions 22.1.3 to 22.7.1 and might just let crafty transactions overreach their limits! Think of it like a restaurant where the chef miscalculates the ingredients for a dish. If the kitchen thinks they have infinite supplies, they might cook up a storm, but if everyone orders wildly different meals, chaos will ensue when the bills come due. If exploited, a single contract could execute with an inflated gas amount, skewing the entire network's consensus. This could lead to transaction failures or even state roots that don’t match reality, potentially catastrophic for the integrity of the network!
Think of it like a restaurant where the chef miscalculates the ingredients for a dish. If the kitchen thinks they have infinite supplies, they might cook up a storm, but if everyone orders wildly different meals, chaos will ensue when the bills come due. This vulnerability stems from an incorrect conversion between 32-bit signed and unsigned numeric types during gas calculations, which can cause executed calls to use inappropriate amounts, resulting in failed transactions and consensus issues.
If exploited, a single contract could execute with an inflated gas amount, skewing the entire network's consensus. This could lead to transaction failures or even state roots that don’t match reality, potentially catastrophic for the integrity of the network! Upgrade your Besu client to version 22.7.1 immediately to avoid these issues. If upgrading isn't feasible, you can revert to version 22.1.3 or earlier as a workaround. Don't let your transactions go rogue! You've got this! Fixing it is straightforward and will help maintain the integrity of your network! 🛡️