Hello,
I am using Azure DevOps and have a repository called Projects. Within this repository, there is a YAML file in which I discovered a plaintext password that was not securely stored.
Fortunately, the repository is approximately three years old, and the password has already been rotated.
I discovered the issue because I use a security scanning tool that identifies critical security findings. The tool reported a critical finding in the Projects repository, specifically in the Apple branch, indicating that an unsecured password had been committed.
To resolve the issue, I opened the YAML file, removed the plaintext password, and committed the changes to the repository.
However, although the password is no longer visible in the current version of the YAML file, my security scanning tool continues to report the same critical finding.
Why is this happening, and what am I doing wrong? How can i solve it with minimal issues?