p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in irrd

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 2

  1. CVE-2026-28681

    Hoch · CVSS 8.1EPSS 0,49%Korrektur verfügbar

    IRRd: web UI host header injection allows password reset poisoning via attacker-controlled email links

    Internet Routing Registry daemon version 4 is an IRR database server, processing IRR objects in the RPSL format. From version 4.4.0 to before version 4.4.5 and from version 4.5.0 to before version 4.5.1, an attacker can manipulate the HTTP Host header on a password reset or account creation request. The confirmation link in the resulting email can then point to an attacker-controlled domain. Opening the link in the email is sufficient to pass the token to the attacker, who can then use it on the real IRRD instance to take over the account. A compromised account can then be used to modify RPSL objects maintained by the account's mntners and pe

    • Auf 4.4.5 aktualisieren
    • Auf 4.5.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2022-24798

    Hoch · CVSS 7.5EPSS 1,42%Korrektur verfügbar

    Insufficient password hash filtering in some IRRd queries and exports

    Internet Routing Registry daemon version 4 is an IRR database server, processing IRR objects in the RPSL format. IRRd did not always filter password hashes in query responses relating to `mntner` objects and database exports. This may have allowed adversaries to retrieve some of these hashes, perform a brute-force search for the clear-text passphrase, and use these to make unauthorised changes to affected IRR objects. This issue only affected instances that process password hashes, which means it is limited to IRRd instances that serve authoritative databases. IRRd instances operating solely as mirrors of other IRR databases are not affected.

    • Auf 4.2.3 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 →