How severe is GHSA-gff2-p6vm-3p8g?

GHSA-gff2-p6vm-3p8g has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-gff2-p6vm-3p8g?

GHSA-gff2-p6vm-3p8g affects the following packages: zendframework/zendframework (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-gff2-p6vm-3p8g?

Update zendframework/zendframework to 2.4.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gff2-p6vm-3p8g is resolved across your whole dependency graph.

How do I detect GHSA-gff2-p6vm-3p8g in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zendframework/zendframework. 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.

How do I mitigate GHSA-gff2-p6vm-3p8g 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-gff2-p6vm-3p8g?

O3 pinpoints whether GHSA-gff2-p6vm-3p8g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-gff2-p6vm-3p8g actively exploited in the wild?

No public exploit code has been indexed for GHSA-gff2-p6vm-3p8g 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-gff2-p6vm-3p8g published, and has it been updated?

GHSA-gff2-p6vm-3p8g was published on June 7, 2024 and was last updated on December 4, 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

GHSA-gff2-p6vm-3p8g

MEDIUM

ZendFramework potential remote code execution in zend-mail via Sendmail adapter

Published

Jun 7, 2024

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐘zendframework/zendframework

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

When using the zend-mail component to send email via the Zend\Mail\Transport\Sendmail transport, a malicious user may be able to inject arbitrary parameters to the system sendmail program. The attack is performed by providing additional quote characters within an address; when unsanitized, they can be interpreted as additional command line arguments, leading to the vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`zendframework/zendframework`	≥ 2.0.0&&< 2.4.11	2.4.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zendframework/zendframework. 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 zendframework/zendframework to 2.4.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gff2-p6vm-3p8g 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-gff2-p6vm-3p8g 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-gff2-p6vm-3p8g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

When using the zend-mail component to send email via the `Zend\Mail\Transport\Sendmail transport`, a malicious user may be able to inject arbitrary parameters to the system sendmail program. The attack is performed by providing additional quote characters within an address; when unsanitized, they can be interpreted as additional command line arguments, leading to the vulnerability.

O3 Security · Impact-Aware SCA

Is GHSA-gff2-p6vm-3p8g in your dependencies?

O3 detects GHSA-gff2-p6vm-3p8g across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works