The contract uses "s_password" to store the secret password. However, it supposes that "private" is enough to keep it secret, but anyone can analyze on-chain the storage and retrieve the secret password.
The only meaningful difference between a public and private variable is that a public variable has a "getter" function to anyone retrieve it's value easily. A private variable is still retriable, the attacker just need to analyze the storage of the smart contract, which would be slot 1 in case of "s_password". So, the secret password is actually visible for anyone.
Any user can retrieve the secret password via smart contract storage review.
Manual Review
Never store sensitive data on-chain. If you really want, at least try to store in as a hash (and the input need to be a hash too).
Private functions and state variables are only visible for the contract they are defined in and not in derived contracts. In this case private doesn't mean secret/confidential
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.