p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in samba · Seite 4

In den letzten 30 Tagen veröffentlichte Sicherheitslücke für samba: 1. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 66

  1. CVE-2019-14861

    Mittel · CVSS 5.3EPSS 2,3%Korrektur verfügbar

    CVE-2019-14861

    All Samba versions 4.x.x before 4.9.17, 4.10.x before 4.10.11 and 4.11.x before 4.11.3 have an issue, where the (poorly named) dnsserver RPC pipe provides administrative facilities to modify DNS records and zones. Samba, when acting as an AD DC, stores DNS records in LDAP. In AD, the default permissions on the DNS partition allow creation of new records by authenticated users. This is used for example to allow machines to self-register in DNS. If a DNS record was created that case-insensitively matched the name of the zone, the ldb_qsort() and dns_name_compare() routines could be confused into reading memory prior to the list of DNS entries w

    • Auf 2:4.3.11+dfsg-0ubuntu0.14.04.20+esm4 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2019-14870

    Mittel · CVSS 5.4EPSS 2,67%Korrektur verfügbar

    CVE-2019-14870

    All Samba versions 4.x.x before 4.9.17, 4.10.x before 4.10.11 and 4.11.x before 4.11.3 have an issue, where the S4U (MS-SFU) Kerberos delegation model includes a feature allowing for a subset of clients to be opted out of constrained delegation in any way, either S4U2Self or regular Kerberos authentication, by forcing all tickets for these clients to be non-forwardable. In AD this is implemented by a user attribute delegation_not_allowed (aka not-delegated), which translates to disallow-forwardable. However the Samba AD DC does not do that for S4U2Self and does set the forwardable flag even if the impersonated client has the not-delegated fla

    • Auf 2:4.3.11+dfsg-0ubuntu0.14.04.20+esm4 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2019-14847

    Mittel · CVSS 4.9EPSS 2,11%Korrektur verfügbar

    CVE-2019-14847

    A flaw was found in samba 4.0.0 before samba 4.9.15 and samba 4.10.x before 4.10.10. An attacker can crash AD DC LDAP server via dirsync resulting in denial of service. Privilege escalation is not possible with this issue.

    • Auf 2:4.3.11+dfsg-0ubuntu0.14.04.20+esm3 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2019-10218

    Mittel · CVSS 5.3EPSS 3,38%Korrektur verfügbar

    CVE-2019-10218

    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 attacker could use this vulnerability to create files outside of the current working directory using the privileges of the client user.

    • Auf 2:4.3.11+dfsg-0ubuntu0.14.04.20+esm3 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2018-16860

    Hoch · CVSS 7.5EPSS 2,49%Korrektur verfügbar

    CVE-2018-16860

    A flaw was found in samba's Heimdal KDC implementation, versions 4.8.x up to, excluding 4.8.12, 4.9.x up to, excluding 4.9.8 and 4.10.x up to, excluding 4.10.3, when used in AD DC mode. A man in the middle attacker could use this flaw to intercept the request to the KDC and replace the user name (principal) in the request with any desired user name (principal) that exists in the KDC effectively obtaining a ticket for that principal.

    • Auf 2:4.3.11+dfsg-0ubuntu0.14.04.20+esm1 aktualisieren
    Veröffentlicht Aktualisiert
  6. USN-3976-4

    Nicht bewertetKorrektur verfügbar

    samba vulnerability

    USN-3976-1 fixed a vulnerability in Samba. The update introduced a regression causing Samba to occasionally crash. This update fixes the problem. Original advisory details: Isaac Boukris and Andrew Bartlett discovered that Samba incorrectly checked S4U2Self packets. In certain environments, a remote attacker could possibly use this issue to escalate privileges.

    • Auf 2:4.3.11+dfsg-0ubuntu0.14.04.20+esm2 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →