CVE-2023-46853

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.

Published: 2023-10-27 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-46853 is rated Moderate Risk (51.9/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.15%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-46853

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-31 0.12% 0.15% +0.04%
2 2025-12-30 0.15% 0.12% -0.04%
3 2025-11-21 — 0.15% —

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-46853

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]

Weakness enumeration for CVE-2023-46853

OS Trackers for CVE-2023-46853

vendor priority summary link
alpine critical CVE-2023-46853: 1 source package rows (memcached); 10 state rows across 3 repos (3.17-main, 3.18-main, edge-main); fixed 0, open 10. https://security.alpinelinux.org/vuln/CVE-2023-46853
debian not yet assigned CVE-2023-46853 not yet assigned priority: Debian including 1 source packages (memcached), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2023-46853
redhat high — https://access.redhat.com/security/cve/CVE-2023-46853
suse medium CVE-2023-46853 severity moderate: SUSE including 6 source package names (memcached, memcached-1.6.22-1.1, memcached-1.6.38-160000.2.2, memcached-devel, memcached-devel-1.6.22-1.1, memcached-devel-1.6.38-160000.2.2), 60 product×package rows across 38 product lines (HPE Helion OpenStack 8, SUSE CaaS Platform 4.0, … (38 product lines)): Known Not Affected 56, Fixed 4. https://www.suse.com/security/cve/CVE-2023-46853/
ubuntu medium CVE-2023-46853 medium priority: Ubuntu including 1 source packages (memcached), 9 status rows across 9 suites (bionic, focal, jammy, lunar, mantic, noble, trusty, upstream, xenial): not-affected 4, released 4, ignored 1. https://ubuntu.com/security/CVE-2023-46853

Affected software / configurations for CVE-2023-46853

Vendor Product Version Raw CPE
memcached memcached < 1.6.22 cpe:2.3:a:memcached:memcached:*:*:*:*:*:*:*:*

References for CVE-2023-46853

cvelogic Threat Intelligence