Normal behaviour is that owner can use update vault
Current behaviour owner cannot update secret, due to move_to overwrite abort.
Likelihood: High
Straightforward path: anyone can call set_secret to change a secret.
The current architecture allows one secret per vault, so the update is the intended behavior.
Impact:
The current architecture allows one secret per vault, so the update is the intended behavior.
Breaks functionality and disrupts the intended path.
This test proves that the owner cannot update the secret because move_to cannot overwrite an existing resource.
This mitigation allows the owner to update the secret or create a vault and set an initial secret. Additionally, this code enforces access restrictions, allowing only the owner to set or update a secret.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.