p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in systemd · Seite 2

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 63

  1. CVE-2022-45873

    Mittel · CVSS 5.5EPSS 0,27%Korrektur verfügbar

    CVE-2022-45873

    systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a long backtrace. This occurs in parse_elf_object in shared/elf-util.c. The exploitation methodology is to crash a binary calling the same function recursively, and put it in a deeply nested directory to make its backtrace large enough to cause the deadlock. This must be done 16 times when MaxConnections=16 is set for the systemd/units/systemd-coredump.socket file.

    • Auf 252-1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2022-2526

    Kritisch · CVSS 9.8EPSS 1,33%Korrektur verfügbar

    CVE-2022-2526

    A use-after-free vulnerability was found in systemd. This issue occurs due to the on_stream_io() function and dns_stream_complete() function in 'resolved-dns-stream.c' not incrementing the reference counting for the DnsStream object. Therefore, other functions and callbacks called can dereference the DNSStream object, causing the use-after-free when the reference is still used later.

    • Auf 240-1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2020-13529

    Mittel · CVSS 6.1EPSS 1,43%Korrektur verfügbar

    CVE-2020-13529

    An exploitable denial-of-service vulnerability exists in Systemd 245. A specially crafted DHCP FORCERENEW packet can cause a server running the DHCP client to be vulnerable to a DHCP ACK spoofing attack. An attacker can forge a pair of FORCERENEW and DCHP ACK packets to reconfigure the server.

    • Auf 249.4-2 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2020-13776

    Mittel · CVSS 6.7EPSS 0,46%Korrektur verfügbar

    CVE-2020-13776

    systemd through v245 mishandles numerical usernames such as ones composed of decimal digits or 0x followed by hex digits, as demonstrated by use of root privileges when privileges of the 0x0 user account were intended. NOTE: this issue exists because of an incomplete fix for CVE-2017-1000082.

    • Auf 246-2 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2020-1712

    Hoch · CVSS 7.8EPSS 0,46%Korrektur verfügbar

    CVE-2020-1712

    A heap use-after-free vulnerability was found in systemd before version v245-rc1, where asynchronous Polkit queries are performed while handling dbus messages. A local unprivileged attacker can abuse this flaw to crash systemd services or potentially execute code and elevate their privileges, by sending specially crafted dbus messages.

    • Auf 244.2-1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2018-21029

    Kritisch · CVSS 9.8EPSS 3,14%Korrektur verfügbar

    CVE-2018-21029

    systemd 239 through 245 accepts any certificate signed by a trusted certificate authority for DNS Over TLS. Server Name Indication (SNI) is not sent, and there is no hostname validation with the GnuTLS backend. NOTE: This has been disputed by the developer as not a vulnerability since hostname validation does not have anything to do with this issue (i.e. there is no hostname to be sent)

    • Auf 244-1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2019-15718

    Mittel · CVSS 5.5EPSS 0,51%Korrektur verfügbar

    CVE-2019-15718

    In systemd 240, bus_open_system_watch_bind_with_description in shared/bus-util.c (as used by systemd-resolved to connect to the system D-Bus instance), calls sd_bus_set_trusted, which disables access controls for incoming D-Bus messages. An unprivileged user can exploit this by executing D-Bus methods that should be restricted to privileged users, in order to change the system's DNS resolver settings.

    • Auf 242-7 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2019-3843

    Mittel · CVSS 4.5EPSS 0,94%Öffentlicher ExploitKorrektur verfügbar

    CVE-2019-3843

    It was discovered that a systemd service that uses DynamicUser property can create a SUID/SGID binary that would be allowed to run as the transient service UID/GID even after the service is terminated. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the UID/GID will be recycled.

    • Auf 242-4 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2019-3844

    Mittel · CVSS 4.5EPSS 0,92%Öffentlicher ExploitKorrektur verfügbar

    CVE-2019-3844

    It was discovered that a systemd service that uses DynamicUser property can get new privileges through the execution of SUID binaries, which would allow to create binaries owned by the service transient group with the setgid bit set. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the GID will be recycled.

    • Auf 242-4 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2019-3842

    Mittel · CVSS 4.5EPSS 1,21%Öffentlicher ExploitKorrektur verfügbar

    CVE-2019-3842

    In systemd before v242-rc4, it was discovered that pam_systemd does not properly sanitize the environment before using the XDG_SEAT variable. It is possible for an attacker, in some particular configurations, to set a XDG_SEAT environment variable which allows for commands to be checked against polkit policies using the "allow_active" element rather than "allow_any".

    • Auf 241-3 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2019-6454

    Mittel · CVSS 5.5EPSS 2,04%Korrektur verfügbar

    CVE-2019-6454

    An issue was discovered in sd-bus in systemd 239. bus_process_object() in libsystemd/sd-bus/bus-objects.c allocates a variable-length stack buffer for temporarily storing the object path of incoming D-Bus messages. An unprivileged local user can exploit this by sending a specially crafted message to PID1, causing the stack pointer to jump over the stack guard pages into an unmapped memory region and trigger a denial of service (systemd PID1 crash and kernel panic).

    • Auf 240-6 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2018-16888

    Mittel · CVSS 4.4EPSS 0,29%Korrektur verfügbar

    CVE-2018-16888

    It was discovered systemd does not correctly check the content of PIDFile files before using it to kill processes. When a service is run from an unprivileged user (e.g. User field set in the service file), a local attacker who is able to write to the PIDFile of the mentioned service may use this flaw to trick systemd into killing other services and/or privileged processes. Versions before v237 are vulnerable.

    • Auf 237-1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2018-16865

    Hoch · CVSS 7.5EPSS 3,02%Korrektur verfügbar

    CVE-2018-16865

    An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the journal socket. A local attacker, or a remote one if systemd-journal-remote is used, may use this flaw to crash systemd-journald or execute code with journald privileges. Versions through v240 are vulnerable.

    • Auf 240-4 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2018-16864

    Hoch · CVSS 7.4EPSS 0,71%Korrektur verfügbar

    CVE-2018-16864

    An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when a program with long command line arguments calls syslog. A local attacker may use this flaw to crash systemd-journald or escalate his privileges. Versions through v240 are vulnerable.

    • Auf 240-4 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 →