Coveralls Token

ID

coveralls_repo_token

Severity

low

Vendor

Coveralls

Family

API Token

Description

Coveralls is a developments tool that helps monitoring code coverage. It uses an API to send the coverage results to its service.

Security

Any hardcoded Coveralls Token is a potential secret reported by this detector.

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

Since the token is associated with Coveralls builds, checking those can give information about a suspicious token usage.

Examples

#!/usr/bin/env bash

echo "Testing $1"
CODE_DIR=$(cd $SCRIPT_DIR/..; pwd)
echo "$@"
$DOCKER_CMD run \
    --rm \
    --name test \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v $CODE_DIR:$CODE_DIR -w $CODE_DIR \
    -e COVERALLS_REPO_TOKEN=wms25r3w3mu4z4e8n3fzatebfuq47kake \
    -e TRAVIS_JOB_ID=$TRAVIS_JOB_ID \
    -e TRAVIS_BRANCH=$TRAVIS_BRANCH \
    -e TRAVIS_PULL_REQUEST=$TRAVIS_PULL_REQUEST \
    -e TRAVIS=$TRAVIS \
    test-container \
    sh -c export PYTHONPATH=\$PYTHONPATH:\$PWD/test ; python test/"$@"

Mitigation / Fix

  1. Remove the Token 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 Account dashboard to revoke the token.

  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://coveralls.io/api/docs