Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,885
Community Members
 
Community Events
168
Community Groups

What to do if you've committed sensitive data to a Bitbucket Cloud repository

Problem

You have accidentally committed a file containing sensitive data.

Background

Security researchers and threat actors alike are actively scanning hosted git repositories like yours, looking for passwords, secrets, and other useful configuration info potentially hiding in your data.

There are several free and openly available tools to automate the discovery of sensitive data across services like Bitbucket Cloud.

Using information found in publicly accessible repositories, attackers can then access and compromise your services and systems, often without your knowledge.

Unfortunately, the process to backtrack a mistake like this is not as straightforward as removing the lines or files in question, so we've outlined some steps for you below.

Solution

You should take the following actions as soon as possible:

  1. Remove the file with the sensitive content from repository, for more details please refer to: https://stackoverflow.com/questions/2047465/how-can-i-delete-a-file-from-a-git-repository

  2. Once the file is removed, you need to make sure you remove it from the repository history as well, it can be done by using the BFG repo cleaner: https://rtyley.github.io/bfg-repo-cleaner/

  3. Push the cleaned repository to Bitbucket remote and raise a support ticket for us to run the GC on the repository (https://support.atlassian.com/contact/#/)

  4. To avoid adding and committing sensitive files back to the repository in the future, we highly recommend adding those file to .gitignore, that way you are sure you do not expose your credentials publicly: https://www.atlassian.com/git/tutorials/saving-changes/gitignore

  5. Rotate any passwords, keys or other credentials to avoid any malicious use following the exposure.

  6. Perform thorough review of all your repositories to ensure any sensitive keys, passwords or other data have been removed. If necessary repeat the steps above to remove any additional files and re-write the repository history.

 

Further Reading

Some further reading on this topic:

1 comment

DPK J Community Leader Feb 05, 2020

Horrible things can happen sometimes :-)

Like # people like this

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

3,499 views 3 10
Read article

Atlassian Community Events