CVE-2017-1000009 — akeneo/pim-community-dev
CRITICALCVE-2017-1000009 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in akeneo/pim-community-dev. A fix is available for akeneo/pim-community-dev — see the affected versions and patch details below.
Akeneo PIM vulnerable to shell injection in the mass edition
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2017-1000009 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
akeneo/pim-community-dev🐘akeneo/pim-community-dev🐘akeneo/pim-community-devReal-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
Akeneo PIM CE and EE <1.6.6, <1.5.15, <1.4.28 are vulnerable to shell injection in the mass edition, resulting in remote execution.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | akeneo/pim-community-dev | ≥ 1.4&&< 1.4.28 | 1.4.28composer require akeneo/pim-community-dev:^1.4.28 |
| 🐘Packagist | akeneo/pim-community-dev | ≥ 1.5&&< 1.5.15 | 1.5.15composer require akeneo/pim-community-dev:^1.5.15 |
| 🐘Packagist | akeneo/pim-community-dev | ≥ 1.6&&< 1.6.6 | 1.6.6composer require akeneo/pim-community-dev:^1.6.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for akeneo/pim-community-dev, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update akeneo/pim-community-dev to 1.4.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000009 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 CVE-2017-1000009 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2017-1000009. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2017-1000009 in your dependencies?
O3 Security finds CVE-2017-1000009 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.