p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in patch

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

RSS ↗
Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 11

  1. CVE-2026-56289

    Mittel · CVSS 4.6EPSS 0,11%Keine Korrektur veröffentlicht

    Loop with Unreachable Exit Condition in GNU patch

    GNU patch is vulnerable to a denial of service (DoS) due to improper validation of hunk (single block of changes in diff) line offsets in unified-diff input. A specially crafted patch can specify an extremely large line number, causing the application to enter an effectively infinite processing loop while attempting to locate the requested position. This results in excessive CPU consumption and prevents the process from completing. An attacker can trigger this behavior by supplying a malicious patch file, causing the utility to become unresponsive and require manual termination. This issue has been fixed in the commit faba04ef4f2b410257f76

    Veröffentlicht Aktualisiert
  2. CVE-2026-56288

    Mittel · CVSS 4.6EPSS 0,11%Keine Korrektur veröffentlicht

    NULL Pointer Dereference in GNU patch

    GNU patch is vulnerable to a NULL pointer dereference when processing a specially crafted unified-diff patch file. Improper handling of consecutive end-of-file newline markers can corrupt internal hunk (single block of changes in diff) data structures, causing the application to pass a NULL pointer to fwrite() during patch processing. An attacker can trigger this condition with a malicious patch file, causing the utility to crash and resulting in a denial of service. This issue has been fixed in the commit e6d6a4e021660679d7fc9150f981d4920f722313

    Veröffentlicht Aktualisiert
  3. CVE-2019-20633

    Mittel · CVSS 5.5EPSS 1,02%Keine Korrektur veröffentlicht

    CVE-2019-20633

    GNU patch through 2.7.6 contains a free(p_line[p_end]) Double Free vulnerability in the function another_hunk in pch.c that can cause a denial of service via a crafted patch file. NOTE: this issue exists because of an incomplete fix for CVE-2018-6952.

    Veröffentlicht Aktualisiert
  4. CVE-2018-20969

    Hoch · CVSS 7.8EPSS 2,68%Korrektur verfügbar

    CVE-2018-20969

    do_ed_script in pch.c in GNU patch through 2.7.6 does not block strings beginning with a ! character. NOTE: this is the same commit as for CVE-2019-13638, but the ! syntax is specific to ed, and is unrelated to a shell metacharacter.

    • Auf 2.7.5-1ubuntu0.16.04.2 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2019-13638

    Hoch · CVSS 7.8EPSS 4,49%Korrektur verfügbar

    CVE-2019-13638

    GNU patch through 2.7.6 is vulnerable to OS shell command injection that can be exploited by opening a crafted patch file that contains an ed style diff payload with shell metacharacters. The ed editor does not need to be present on the vulnerable system. This is different from CVE-2018-1000156.

    • Auf 2.7.5-1ubuntu0.16.04.2 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2018-1000156

    Hoch · CVSS 7.8EPSS 5,33%Korrektur verfügbar

    CVE-2018-1000156

    GNU Patch version 2.7.6 contains an input validation vulnerability when processing patch files, specifically the EDITOR_PROGRAM invocation (using ed) can result in code execution. This attack appear to be exploitable via a patch file processed via the patch utility. This is similar to FreeBSD's CVE-2015-1418 however although they share a common ancestry the code bases have diverged over time.

    • Auf 2.7.5-1ubuntu0.16.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2018-6951

    Hoch · CVSS 7.5EPSS 8,36%Korrektur verfügbar

    CVE-2018-6951

    An issue was discovered in GNU patch through 2.7.6. There is a segmentation fault, associated with a NULL pointer dereference, leading to a denial of service in the intuit_diff_type function in pch.c, aka a "mangled rename" issue.

    • Auf 2.7.5-1ubuntu0.16.04.1 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 →