You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Objectarium contract, there is a discrepancy in how compressed sizes are handled during the lifecycle of an object. While the store_object function correctly increments the compressed_size statistic upon storing an object, the corresponding decrement operation is missing in the forget_object function when an object is removed. This oversight leads to inaccurate tracking of the compressed data size within the system.
Recommendation
To resolve this issue, update the forget_object function to include a decrement operation for the compressed_size stat similar to how it handles other metrics.
The text was updated successfully, but these errors were encountered:
Note
Severity: Low
target: v5.0.0 - Commit: cde785fbd2dad71608d53f8524e0ef8c8f8178af
Ref: OKP4 CosmWasm Audit Report v1.0 - 02-05-2024 - BlockApex
Description
In the Objectarium contract, there is a discrepancy in how compressed sizes are handled during the lifecycle of an object. While the
store_object
function correctly increments thecompressed_size
statistic upon storing an object, the corresponding decrement operation is missing in theforget_object
function when an object is removed. This oversight leads to inaccurate tracking of the compressed data size within the system.Recommendation
To resolve this issue, update the forget_object function to include a decrement operation for the
compressed_size
stat similar to how it handles other metrics.The text was updated successfully, but these errors were encountered: