GHSA-2cxf-6567-7pp6
LOWGHSA-2cxf-6567-7pp6 is a low-severity (CVSS 3) vulnerability in com.datadoghq:datadog-api-client. O3 Security confirms whether GHSA-2cxf-6567-7pp6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Local Information Disclosure Vulnerability
Real-World Exposure
com.datadoghq:datadog-api-clientReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Local information disclosure of sensitive information downloaded via the API using the API Client.
Finding
The Datadog API is executed on a unix-like system with multiple users. The API is used to download a file containing sensitive information. This sensitive information is exposed locally to other users. This vulnerability exists in the API Client for version 1 and 2. The method prepareDownloadFilecreates creates a temporary file with the permissions bits of -rw-r--r-- on unix-like systems. On unix-like systems, the system temporary directory is shared between users. As such, the contents of the file downloaded via the downloadFileFromResponse method will be visible to all other users on the local system.
Analysis of the finding determined that the affected code was unused, meaning that the exploitation likelihood is low. The unused code has been removed, effectively mitigating this issue.
This vulnerability was found due to this query that Jonathan Leitschuh contributed to the Semmle QL project.
Patches
This issue has been patched in version 1.0.0-beta.9.
See also Remove unused downloadFile helpers.
Workarounds
The recommended workaround is to specify java.io.tmpdir when starting the JVM with the flag -Djava.io.tmpdir, specifying a path to a directory with drw------- permissions owned by dd-agent.
References
- CWE-378: Creation of Temporary File With Insecure Permissions
- CWE-379: Creation of Temporary File in Directory with Insecure Permissions
For more information
If you have any questions or comments about this advisory:
- Open an issue in DataDog/datadog-api-client-java
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.datadoghq:datadog-api-client | ≥ 1.0.0-beta.6&&< 1.0.0-beta.9 | 1.0.0-beta.9 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.datadoghq:datadog-api-client. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.datadoghq:datadog-api-client to 1.0.0-beta.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2cxf-6567-7pp6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2cxf-6567-7pp6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-2cxf-6567-7pp6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2cxf-6567-7pp6 in your dependencies?
O3 detects GHSA-2cxf-6567-7pp6 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.