Memcached 1.5
Memcached 1.5
The Memcached 1.5 reached end of service life on Mar 9, 2020 — Memcached 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 Memcached 1.5 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
- memcached
- release
- 1.5
- product Label
- Memcached
- release Label
- 1.5
- codename
- lts
- latest Version
- 1.5.22
- release Date
- 2017-07-21
- maintained
- source Url
- https://endoflife.date/memcached
Lifecycle Dates
- End of Service Life
- Mar 9, 2020
- Last OEM Support
- Mar 9, 2020
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Memcached 1.5 — 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 Memcached 1.5?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Memcached 1.5 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.
Memcached 1.5 Support: Frequently Asked Questions
Is the Memcached 1.5 still supported?
Memcached ended support for the Memcached 1.5 on Mar 9, 2020 — 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 Memcached 1.5 end of service life (EOSL) date?
Memcached lists the end of service life for the Memcached 1.5 as Mar 9, 2020.
Can I keep using the Memcached 1.5 after its EOSL date?
Yes. EOSL means Memcached 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 Memcached 1.5 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 Memcached 1.5
7 published CVEs affect the Memcached 1.5, including 7 rated critical or high severity. Memcached no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2023-46853 | CRITICAL | 9.8 | Oct 27, 2023 | In Memcached before 1.6.22, an off-by-one error exists when processing proxy requests in proxy mode, if \n is used instead of \r\n. |
| CVE-2026-47784 | HIGH | 8.1 | May 20, 2026 | In memcached before 1.6.42, password data for SASL password database authentication has a timing side channel because memcmp is used by sasl_server_userdb_checkpass. |
| CVE-2026-47783 | HIGH | 8.1 | May 20, 2026 | In memcached before 1.6.42, username data for SASL password database authentication has a timing side channel because a loop exits as soon as a valid username is found by sasl_server_userdb_checkpass. |
| CVE-2023-46852 | HIGH | 7.5 | Oct 27, 2023 | In Memcached before 1.6.22, a buffer overflow exists when processing multiget requests in proxy mode, if there are many spaces after the "get" substring. |
| CVE-2019-15026 | HIGH | 7.5 | Aug 30, 2019 | memcached 1.5.16, when UNIX sockets are used, has a stack-based buffer over-read in conn_to_str in memcached.c. |
| CVE-2019-11596 | HIGH | 7.5 | Apr 29, 2019 | In memcached before 1.5.14, a NULL pointer dereference was found in the "lru mode" and "lru temp_ttl" commands. This causes a denial of service when parsing crafted lru command messages in process_lru_command in memcached.c. |
| CVE-2018-1000115 | HIGH | 7.5 | Mar 5, 2018 | Memcached version 1.5.5 contains an Insufficient Control of Network Message Volume (Network Amplification, CWE-406) vulnerability in the UDP support of the memcached server that can result in denial of service via network flood (traffic amplification of 1:50,000 has been reported by reliable sources). This attack appear to be exploitable via network connectivity to port 11211 UDP. This vulnerability appears to have been fixed in 1.5.6 due to the disabling of the UDP protocol by default. |