API Token Exposure via Build Process in Black Duck blackduck-c-cpp
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Black Duck | blackduck-c-cpp | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Black Duck | Blackduck-c-cpp |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.184% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Title | API Token Exposure via Build Process in Black Duck blackduck-c-cpp | |
| First Time appeared |
Black Duck
Black Duck blackduck-c-cpp |
|
| Vendors & Products |
Black Duck
Black Duck blackduck-c-cpp |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Invocation of Process Using Visible Sensitive Information in Black Duck blackduck-c-cpp 1.0.17 through 3.0.6 allows an actor able to execute code within the scanned project's build to obtain the Black Duck API token via the ambient process environment, which is inherited by subprocesses launched during build capture and signature scanning. This applies only where the token is supplied through the BLACKDUCK_API_TOKEN or BD_HUB_TOKEN environment variable. Upgrading does not remediate prior disclosure; any token supplied to an affected version through an environment variable should be rotated. | |
| Weaknesses | CWE-214 | |
| References |
| |
| Metrics |
cvssV4_0
|