How severe is GHSA-qvgg-r6rq-vwfx?

No CVSS score has been assigned to GHSA-qvgg-r6rq-vwfx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qvgg-r6rq-vwfx?

GHSA-qvgg-r6rq-vwfx affects the following packages: datadog/dd-trace (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-qvgg-r6rq-vwfx?

Update datadog/dd-trace to 0.30.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qvgg-r6rq-vwfx is resolved across your whole dependency graph.

How do I detect GHSA-qvgg-r6rq-vwfx in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for datadog/dd-trace, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qvgg-r6rq-vwfx if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-qvgg-r6rq-vwfx?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qvgg-r6rq-vwfx can be triaged on real exposure rather than presence alone.

Is GHSA-qvgg-r6rq-vwfx actively exploited in the wild?

No public exploit code has been indexed for GHSA-qvgg-r6rq-vwfx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-qvgg-r6rq-vwfx published, and has it been updated?

GHSA-qvgg-r6rq-vwfx was published on May 15, 2024 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-qvgg-r6rq-vwfx — datadog/dd-trace

Fix: DataDog/dd-trace-php#579

GHSA-qvgg-r6rq-vwfx is a security vulnerability in datadog/dd-trace. A fix is available for datadog/dd-trace — see the affected versions and patch details below.

datadog/dd-trace Circumvents open_basedir INI directive

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘datadog/dd-trace

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

datadog/dd-trace versions 0.30.0 prior to 0.30.2 are affected by a security and stability issue outlined in PR #579. This pull request ensures that the ddtrace.request_init_hook remains bound by the open_basedir INI directive, effectively addressing potential vulnerabilities related to open_basedir restrictions. The update introduces a sandboxing mechanism to isolate the request init hook from errors or exceptions during execution, enhancing the library's stability and preventing adverse impacts on the main script.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`datadog/dd-trace`	≥ 0.30.0&&< 0.30.2	0.30.2`composer require datadog/dd-trace:^0.30.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for datadog/dd-trace, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update datadog/dd-trace to 0.30.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qvgg-r6rq-vwfx 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qvgg-r6rq-vwfx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-qvgg-r6rq-vwfx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

datadog/dd-trace versions 0.30.0 prior to 0.30.2 are affected by a security and stability issue outlined in PR [#579](https://github.com/DataDog/dd-trace-php/pull/579). This pull request ensures that the ddtrace.request_init_hook remains bound by the open_basedir INI directive, effectively addressing potential vulnerabilities related to open_basedir restrictions. The update introduces a sandboxing mechanism to isolate the request init hook from errors or exceptions during execution, enhancing the library's stability and preventing adverse impacts on the main script.

O3 Security · Impact-Aware SCA

Is GHSA-qvgg-r6rq-vwfx in your dependencies?

O3 Security finds GHSA-qvgg-r6rq-vwfx across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works