The contract stores sensitive data, such as private keys or passwords, in an unencrypted format, which can expose sensitive information to potential attackers.
The contract directly stores sensitive data, such as private keys or passwords, without encrypting them. Storing sensitive data in plain text makes it susceptible to unauthorized access and compromises the security of the contract and its users.
Unencrypted sensitive data can be easily accessed and exploited by attackers. This can lead to unauthorized access to accounts, funds, and other sensitive resources associated with the contract, resulting in potential financial losses and security breaches.
Manual
Avoid Hard-Coding Sensitive Data: Refrain from hard-coding sensitive data, such as private keys or passwords, directly into the contract's source code.
Utilize Encryption: If sensitive data is required for contract functionality, consider using encryption techniques to secure the data before storage. Utilize libraries like OpenZeppelin's Encrypt.sol to encrypt sensitive information before storing it on-chain.
External Key Management: Whenever possible, manage sensitive data externally, off-chain, using secure key management solutions. This reduces the risk of exposing sensitive data on the blockchain.
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.