rpm package
suse/samba&distro=SUSE Linux Enterprise Server 12 SP1-LTSS
pkg:rpm/suse/samba&distro=SUSE%20Linux%20Enterprise%20Server%2012%20SP1-LTSS
Vulnerabilities (9)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2019-10218 | — | < 4.2.4-28.36.1 | 4.2.4-28.36.1 | Nov 6, 2019 | A flaw was found in the samba client, all samba versions before samba 4.11.2, 4.10.10 and 4.9.15, where a malicious server can supply a pathname to the client with separators. This could allow the client to access files and folders outside of the SMB network pathnames. An attacke | ||
| CVE-2019-3880 | — | < 4.2.4-28.32.1 | 4.2.4-28.32.1 | Apr 9, 2019 | A flaw was found in the way samba implemented an RPC endpoint emulating the Windows registry service API. An unprivileged attacker could use this flaw to create a new registry hive file anywhere they have unix permissions which could lead to creation of a new file in the Samba sh | ||
| CVE-2018-10858 | — | < 4.2.4-28.29.1 | 4.2.4-28.29.1 | Aug 22, 2018 | A heap-buffer overflow was found in the way samba clients processed extra long filename in a directory listing. A malicious samba server could use this flaw to cause arbitrary code execution on a samba client. Samba versions before 4.6.16, 4.7.9 and 4.8.4 are vulnerable. | ||
| CVE-2017-12151 | — | < 4.2.4-28.19.3 | 4.2.4-28.19.3 | Jul 27, 2018 | A flaw was found in the way samba client before samba 4.4.16, samba 4.5.14 and samba 4.6.8 used encryption with the max protocol set as SMB3. The connection could lose the requirement for signing and encrypting to any DFS redirects, allowing an attacker to read or alter the conte | ||
| CVE-2017-12150 | — | < 4.2.4-28.19.3 | 4.2.4-28.19.3 | Jul 26, 2018 | It was found that samba before 4.4.16, 4.5.x before 4.5.14, and 4.6.x before 4.6.8 did not enforce "SMB signing" when certain configuration options were enabled. A remote attacker could launch a man-in-the-middle attack and retrieve information in plain-text. | ||
| CVE-2017-12163 | — | < 4.2.4-28.19.3 | 4.2.4-28.19.3 | Jul 26, 2018 | An information leak flaw was found in the way SMB1 protocol was implemented by Samba before 4.4.16, 4.5.x before 4.5.14, and 4.6.x before 4.6.8. A malicious client could use this flaw to dump server memory contents to a file on the samba share or to a shared printer, though the e | ||
| CVE-2018-1050 | — | < 4.2.4-28.29.1 | 4.2.4-28.29.1 | Mar 13, 2018 | All versions of Samba from 4.0.0 onwards are vulnerable to a denial of service attack when the RPC spoolss service is configured to be run as an external daemon. Missing input sanitization checks on some of the input parameters to spoolss RPC calls could cause the print spooler s | ||
| CVE-2017-15275 | Hig | 7.5 | < 4.2.4-28.24.1 | 4.2.4-28.24.1 | Nov 27, 2017 | Samba before 4.7.3 might allow remote attackers to obtain sensitive information by leveraging failure of the server to clear allocated heap memory. | |
| CVE-2017-14746 | Cri | 9.8 | < 4.2.4-28.24.1 | 4.2.4-28.24.1 | Nov 27, 2017 | Use-after-free vulnerability in Samba 4.x before 4.7.3 allows remote attackers to execute arbitrary code via a crafted SMB1 request. |
- CVE-2019-10218Nov 6, 2019affected < 4.2.4-28.36.1fixed 4.2.4-28.36.1
A flaw was found in the samba client, all samba versions before samba 4.11.2, 4.10.10 and 4.9.15, where a malicious server can supply a pathname to the client with separators. This could allow the client to access files and folders outside of the SMB network pathnames. An attacke
- CVE-2019-3880Apr 9, 2019affected < 4.2.4-28.32.1fixed 4.2.4-28.32.1
A flaw was found in the way samba implemented an RPC endpoint emulating the Windows registry service API. An unprivileged attacker could use this flaw to create a new registry hive file anywhere they have unix permissions which could lead to creation of a new file in the Samba sh
- CVE-2018-10858Aug 22, 2018affected < 4.2.4-28.29.1fixed 4.2.4-28.29.1
A heap-buffer overflow was found in the way samba clients processed extra long filename in a directory listing. A malicious samba server could use this flaw to cause arbitrary code execution on a samba client. Samba versions before 4.6.16, 4.7.9 and 4.8.4 are vulnerable.
- CVE-2017-12151Jul 27, 2018affected < 4.2.4-28.19.3fixed 4.2.4-28.19.3
A flaw was found in the way samba client before samba 4.4.16, samba 4.5.14 and samba 4.6.8 used encryption with the max protocol set as SMB3. The connection could lose the requirement for signing and encrypting to any DFS redirects, allowing an attacker to read or alter the conte
- CVE-2017-12150Jul 26, 2018affected < 4.2.4-28.19.3fixed 4.2.4-28.19.3
It was found that samba before 4.4.16, 4.5.x before 4.5.14, and 4.6.x before 4.6.8 did not enforce "SMB signing" when certain configuration options were enabled. A remote attacker could launch a man-in-the-middle attack and retrieve information in plain-text.
- CVE-2017-12163Jul 26, 2018affected < 4.2.4-28.19.3fixed 4.2.4-28.19.3
An information leak flaw was found in the way SMB1 protocol was implemented by Samba before 4.4.16, 4.5.x before 4.5.14, and 4.6.x before 4.6.8. A malicious client could use this flaw to dump server memory contents to a file on the samba share or to a shared printer, though the e
- CVE-2018-1050Mar 13, 2018affected < 4.2.4-28.29.1fixed 4.2.4-28.29.1
All versions of Samba from 4.0.0 onwards are vulnerable to a denial of service attack when the RPC spoolss service is configured to be run as an external daemon. Missing input sanitization checks on some of the input parameters to spoolss RPC calls could cause the print spooler s
- affected < 4.2.4-28.24.1fixed 4.2.4-28.24.1
Samba before 4.7.3 might allow remote attackers to obtain sensitive information by leveraging failure of the server to clear allocated heap memory.
- affected < 4.2.4-28.24.1fixed 4.2.4-28.24.1
Use-after-free vulnerability in Samba 4.x before 4.7.3 allows remote attackers to execute arbitrary code via a crafted SMB1 request.