Pigeonhole 0.2
Pigeonhole 0.2
The Pigeonhole 0.2 reached end of service life on May 9, 2013 — Pigeonhole 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 Pigeonhole 0.2 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
- pigeonhole
- release
- 0.2
- product Label
- Pigeonhole
- release Label
- 0.2
- codename
- lts
- latest Version
- 0.2.5
- release Date
- 2010-09-10
- maintained
- source Url
- https://endoflife.date/pigeonhole
Lifecycle Dates
- End of Service Life
- May 9, 2013
- Last OEM Support
- May 9, 2013
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Pigeonhole 0.2 — 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 Pigeonhole 0.2?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Pigeonhole 0.2 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.
Pigeonhole 0.2 Support: Frequently Asked Questions
Is the Pigeonhole 0.2 still supported?
Pigeonhole ended support for the Pigeonhole 0.2 on May 9, 2013 — 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 Pigeonhole 0.2 end of service life (EOSL) date?
Pigeonhole lists the end of service life for the Pigeonhole 0.2 as May 9, 2013.
Can I keep using the Pigeonhole 0.2 after its EOSL date?
Yes. EOSL means Pigeonhole 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 Pigeonhole 0.2 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 Pigeonhole 0.2
1 published CVE affects the Pigeonhole 0.2, including 1 rated critical or high severity. Pigeonhole no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2019-11500 | CRITICAL | 9.8 | Aug 29, 2019 | In Dovecot before 2.2.36.4 and 2.3.x before 2.3.7.2 (and Pigeonhole before 0.5.7.2), protocol processing can fail for quoted strings. This occurs because '\0' characters are mishandled, and can lead to out-of-bounds writes and remote code execution. |