DigitalOcean Spaces Keys

ID

digital_ocean_spaces_key2

Severity

critical

Vendor

Digital Ocean

Family

API Token

Description

DigitalOcean is a cloud infrastructure provider which provides developers, startups, and SMBs with cloud infrastructure-as-a-service platforms.

It provides an API to programmatically access its products and services where a user can manage all the features available in the control panel.

This detector looks for an access key that is not secret, and a secret key that must remain private.

Security

Any hardcoded Digital Ocean access key is a potential secret reported by this detector.

Accidentally checking-in the key to source control repositories could compromise your Digital Ocean account.

The Digital Ocean Dashboard provides a list of all actions (login, resource creation and deletion) that happened in the last 12 months. This can be accessed from the My Profile/Security section of the dashboard.

Examples

do_id: 0EU3HDH7WCUW5V19BVZ8
do_secret: WMmOdI+PREdyOPPt83uj6JlmSI7wW/6Ap7W0MUMsmPI

Mitigation / Fix

  1. Remove the credential from the source code or committed configuration file.

  2. Follow your policy for handling leaked secrets, which typically require revoking the secret in the target system(s). Go to your dashboard to revoke the credential.

  3. If under a git repository, you may remove unwanted files from the repository history using tools like git filter-repo or BFG Repo-Cleaner. You may follow the procedure listed here for GitHub.

You should consider any sensitive data in commits with secrets as compromised.

Remember that secrets may be removed from history in your projects, but not in other users' cloned or forked repositories.

Reference

https://docs.digitalocean.com/reference/api/spaces-api/