35 matches found
ALPINE-CVE-2017-12150
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...
Apple Mac OS X Security Updates (HT208692)-02
Apple Mac OS X is prone to multiple vulnerabilities. SPDX-FileCopyrightText: 2018 Greenbone AG Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-only ifdescription...
openSUSE Security Update : samba (openSUSE-2017-1316)
This update for samba fixes the following issues : Security issues fixed : - CVE-2017-14746: Use-after-free vulnerability bsc1060427. - CVE-2017-15275: Server heap memory information leak bsc1063008. - CVE-2017-12163: Prevent client short SMB1 write from writing server memory to file bsc1058624. ...
SUSE-SU-2017:2971-1 Security update for samba
This update for samba fixes several issues. These security issues were fixed: - CVE-2017-12163: Prevent client short SMB1 write from writing server memory to file, leaking information from the server to the client bsc1058624. - CVE-2017-12150: Always enforce smb signing when it is configured...
samba: Some code path don't enforce smb signing, when they should (incomplete fix of CVE-2017-12150)
It was discovered that the fix for CVE-2017-12150 was not properly shipped in erratum RHSA-2017:2858 for Red Hat Gluster Storage 3.3 for RHEL 6...
SUSE-SU-2017:2726-1 Security update for samba
This update for samba fixes several issues. These security issues were fixed: - CVE-2017-12163: Prevent client short SMB1 write from writing server memory to file, leaking information from the server to the client bsc1058624. - CVE-2017-12150: Always enforce smb signing when it is configured...
SUSE-SU-2017:2715-1 Security update for samba
This update for samba fixes several issues. These security issues were fixed: - CVE-2017-12163: Prevent client short SMB1 write from writing server memory to file, leaking information from the server to the client bsc1058624 - CVE-2017-12150: Always enforce smb signing when it is configured...
Medium: samba
Issue Overview: Server memory information leak over SMB1: An information leak flaw was found in the way SMB1 protocol was implemented by Samba. 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 exact area of serve...
samba: Some code path don't enforce smb signing, when they should
It was found that samba 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...
samba: Some code path don't enforce smb signing, when they should
It was found that samba 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...
samba: Some code path don't enforce smb signing, when they should
It was found that samba 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...
samba: Some code path don't enforce smb signing, when they should
It was found that samba 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...
Design/Logic Flaw
NetApp Clustered Data ONTAP allows man-in-the-middle attackers to obtain sensitive information, gain privileges, or cause a denial of service by leveraging failure to enable SMB signing enforcement in its default state...
samba: Samba based active directory domain controller does not enforce smb signing
It was discovered that Samba did not enforce Server Message Block SMB signing for clients using the SMB1 protocol. A man-in-the-middle attacker could use this flaw to modify traffic between a client and a server...
apache-cxf: Apache CXF does not verify that elements were signed / encrypted by a particular Supporting Token
Apache CXF 2.4.x before 2.4.8, 2.5.x before 2.5.4, and 2.6.x before 2.6.1, when a Supporting Token specifies a child WS-SecurityPolicy 1.1 or 1.2 policy, does not properly ensure that an XML element is signed or encrypted, which has unspecified impact and attack vectors...