Jenkins API Token detected in code

Rule Details

Cortex AppSec Rule ID	APPSEC_SECRET_268
Category	Secrets
Severity	LOW
Framework	Git

Impact

The Jenkins API Token is generated for programmatic API access to the CI/CD controller.

An exposed token can be exploited to achieve Remote Code Execution (RCE) on the controller, extract encrypted secrets, or trigger unauthorized build and deployment processes.

How to Fix

To remediate exposed Source Control or CI/CD tokens:

1. Log in to the relevant system or provider.
2. Navigate to the settings menu to locate the exposed credential.
3. Revoke or delete the compromised token immediately.
4. Generate a new token if continued access is required.
5. Update any dependent systems or services with the new credential.

Next, remove the secret from your codebase:

1. Locate the exposed secret in your codebase.
2. Replace the hardcoded value with a secure variable or reference.

Finally, clean your version control history:

1. Permanently remove the sensitive data from your version control history to ensure it cannot be retrieved.