Secret Vault on Aptos

First Flight #46
Beginner FriendlyWallet
100 EXP
View results
Submission Details
Impact: low
Likelihood: medium
Invalid

Hardcoded Development Addresses in Move.toml Can Lead to Misconfiguration and Predictable Deployment

Hardcoded Development Addresses in Move.toml Can Lead to Misconfiguration and Predictable Deployment

Description

  • Normally, module and dev addresses should be configurable and environment-specific.

  • In this move.toml, development addresses are hardcoded, which can reveal predictable module or account locations and may cause misconfiguration if deployed in a production. These values can be easy retrieve once deployed on chain.

[dev-addresses]
@>owner = "0xcc" # Hardcoded development address
@>secret_vault = "0x0234" # Hardcoded development address

Risk

Likelihood: Medium

  • Test or development addresses are used in code pushed to repositories or accidentally deployed.

  • External parties can discover predictable addresses and perform reconnaissance.

Impact: Low

  • Can facilitate chain scanning and early reconnaissance

Proof of Concept

Observing the Move.toml file, an auditor can directly see:

owner = "0xcc"
secret_vault = "0x0234"

Recommended Mitigation

It is recommended to avoid hardcoding development addresses. Instead, use placeholders or environment-specific configurations to prevent accidental exposure or misuse.

- [dev-addresses]
- owner = "0xcc"
- secret_vault = "0x0234"
+ [dev-addresses]
+ owner = "_"
+ secret_vault = "_"
Updates

Lead Judging Commences

bube Lead Judge 17 days ago
Submission Judgement Published
Invalidated
Reason: Non-acceptable severity

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.