Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:HSummary
CVE-2023-5568 is a medium-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Samba Samba. Its CVSS base score is 5.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 27% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
A heap-based buffer overflow vulnerability, tracked as CVE-2023-5568 and also associated with CWE-122 and CWE-787, affects the Samba file and print server software. The flaw permits a remote, authenticated attacker to trigger a denial of service condition, as reflected in its CVSS 3.1 score of 5.9 requiring high attack complexity and low privileges.
An authenticated remote attacker can send specially crafted requests over the network to the affected Samba instance, resulting in memory corruption that crashes the service and disrupts availability while leaving confidentiality and most integrity properties intact.
Public advisories reference fixes included in Samba 4.19.2 along with Red Hat and Samba bug trackers that document the issue and direct administrators to updated packages for mitigation.
The associated EPSS score reached a peak of 0.1224 with a current value of 0.1035, indicating moderate and relatively stable exploitation interest following disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-57867
Vulnerability Data
A heap-based Buffer Overflow flaw was discovered in Samba. It could allow a remote, authenticated attacker to exploit this vulnerability to cause a denial of service.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.4.1
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.
Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.
Timely patching removes known heap-overflow instances after they exist.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect heap overflows before release.
Secure development lifecycle mandates practices that reduce the likelihood of introducing heap overflows.
Application security requirements can specify bounds-checking and safe memory APIs that mitigate heap overflows.
Secure architecture and engineering principles include memory-safety and input-validation controls that address heap overflows.
Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.
Change management can enforce review gates that catch unsafe memory operations before deployment.