Akeneo PIM 1.5 (Fresh Hare)
Akeneo PIM 1.5 (Fresh Hare)
The Akeneo PIM 1.5 (Fresh Hare) reached end of service life on Sep 30, 2017 — Akeneo PIM no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Akeneo PIM 1.5 (Fresh Hare) incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- akeneo-pim
- release
- 1.5
- product Label
- Akeneo PIM
- release Label
- 1.5 (Fresh Hare)
- codename
- Fresh Hare
- lts
- latest Version
- 1.5.27
- release Date
- 2016-03-15
- maintained
- source Url
- https://endoflife.date/akeneo-pim
Lifecycle Dates
- End of Service Life
- Sep 30, 2017
- Last OEM Support
- Sep 30, 2017
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Akeneo PIM 1.5 (Fresh Hare) — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Akeneo PIM 1.5 (Fresh Hare)?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Akeneo PIM 1.5 (Fresh Hare) when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Akeneo PIM 1.5 (Fresh Hare) Support: Frequently Asked Questions
Is the Akeneo PIM 1.5 (Fresh Hare) still supported?
Akeneo PIM ended support for the Akeneo PIM 1.5 (Fresh Hare) on Sep 30, 2017 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Akeneo PIM 1.5 (Fresh Hare) end of service life (EOSL) date?
Akeneo PIM lists the end of service life for the Akeneo PIM 1.5 (Fresh Hare) as Sep 30, 2017.
Can I keep using the Akeneo PIM 1.5 (Fresh Hare) after its EOSL date?
Yes. EOSL means Akeneo PIM stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Akeneo PIM 1.5 (Fresh Hare) cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Akeneo PIM 1.5 (Fresh Hare)
2 published CVEs affect the Akeneo PIM 1.5 (Fresh Hare), including 2 rated critical or high severity. Akeneo PIM no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2017-1000009 | CRITICAL | 9.8 | Jul 17, 2017 | 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. |
| CVE-2022-46157 | HIGH | 8.8 | Dec 9, 2022 | Akeneo PIM is an open source Product Information Management (PIM). Akeneo PIM Community Edition versions before v5.0.119 and v6.0.53 allows remote authenticated users to execute arbitrary PHP code on the server by uploading a crafted image. Akeneo PIM Community Edition after the versions aforementioned provides patched Apache HTTP server configuration file, for docker setup and in documentation sample, to fix this vulnerability. Community Edition users must change their Apache HTTP server conf |