Vulnerability in Memcached (CVE-2018-1000115)
Summary
Vulnerability in Memcached (CVE-2018-1000115). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.5.6 or later.
Original description
The description as published by the source.
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.
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2018-1000115 has been found in Memcached.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Memcached to 1.5.6 or later.
If unsure, ask your IT team or search "Memcached CVE-2018-1000115" on the vendor's site.
CVE-2018-1000115 (Memcached)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.5.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in Memcached.
Check the vendor advisory for the affected versions of Memcached.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.5.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Memcached' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Memcached' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Memcachedを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Memcached to 1.5.6ステージング環境で 1.5.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory blogs.akamai.com
- advisory github.com
- advisory twitter.com
- advisory usn.ubuntu.com
- advisory debian.org
- advisory synology.com
- patch github.com
- report github.com
- report exploit-db.com
- report exploit-db.com