How to fix: JFrog Artifactory API key in source
Artifactory access tokens and encrypted passwords grant upload, delete, and admin over artifact repositories.
Why it matters
An exposed JFrog Artifactory token can be used to upload malicious artifacts, overwrite existing package versions with backdoored builds, delete critical artifacts, or exfiltrate proprietary build outputs, a supply-chain attack on your internal build system.
Artifactory access tokens and encrypted passwords grant upload, delete, and admin over artifact repositories.
How to fix it
- 1Revoke the token in JFrog Platform → Administration → User Management → Access Tokens
- 2Audit recent artifact uploads for unauthorized changes
- 3Use short-lived access tokens (TTL < 1 hour) for CI/CD pipelines
Code examples
JFrog CLI: rotate access token
# Revoke the compromised token (requires admin token)
curl -X DELETE \
-H 'Authorization: Bearer ADMIN_TOKEN' \
'https://your-org.jfrog.io/access/api/v1/tokens/COMPROMISED_TOKEN_ID'
# Create a short-lived token for CI (expires in 1 hour)
curl -X POST \
-H 'Authorization: Bearer ADMIN_TOKEN' \
-d '{"expires_in": 3600, "scope": "applied-permissions/user"}' \
'https://your-org.jfrog.io/access/api/v1/tokens'References
Detected automatically by VulnRadar. The check id is secret-jfrog-api-key, stable across every scan so you can filter or diff on it.
More secrets checks
Questions
- How severe is JFrog Artifactory API key in source?
- VulnRadar rates this critical severity in the secrets category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id secret-jfrog-api-key, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does JFrog Artifactory API key in source map to?
- It maps to CWE-798. In the OWASP Top 10 it falls under A07:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.