5504 matches found
CVE-2024-52616
CVE-2024-52616 affects the Avahi-daemon. The vulnerability arises because DNS transaction IDs are initialized randomly only at startup and then incremented, making it possible for an attacker to predict IDs and perform DNS spoofing. The connected documents confirm the issue and reference the same...
CVE-2024-52616
A flaw was found in the Avahi-daemon, where it initializes DNS transaction IDs randomly only once at startup, incrementing them sequentially after that. This predictable behavior facilitates DNS spoofing attacks, allowing attackers to guess transaction IDs...
CVE-2024-52616: Small Space of Random Values
A flaw was found in the Avahi-daemon, where it initializes DNS transaction IDs randomly only once at startup, incrementing them sequentially after that. This predictable behavior facilitates DNS spoofing attacks, allowing attackers to guess transaction IDs...
SUSE CVE-2024-52616
A flaw was found in the Avahi-daemon, where it initializes DNS transaction IDs randomly only once at startup, incrementing them sequentially after that. This predictable behavior facilitates DNS spoofing attacks, allowing attackers to guess transaction IDs...
Security update for SUSE Manager Salt Bundle
This update fixes the following issues: venv-salt-minion: Security fixes on Python 3.11 interpreter: CVE-2024-7592: Fixed quadratic complexity in parsing -quoted cookie values with backslashes bsc1229873, bsc1230059 CVE-2024-8088: Prevent malformed payload to cause infinite loops in zipfile.Path...
CVE-2024-52913
In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled...
CVE-2024-52914
In Bitcoin Core before 0.18.0, a node could be stalled for hours when processing the orphans of a crafted unconfirmed transaction...
CVE-2024-52913
In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled...
CVE-2024-52913
In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled...
CVE-2024-52913
In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled...
CVE-2024-52913
In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled...
CVE-2024-52914: Allocation of Resources Without Limits or Throttling
In Bitcoin Core before 0.18.0, a node could be stalled for hours when processing the orphans of a crafted unconfirmed transaction...
CVE-2024-52914
In Bitcoin Core before 0.18.0, a node could be stalled for hours when processing the orphans of a crafted unconfirmed transaction...
PT-2024-35481
Name of the Vulnerable Software and Affected Versions: Bitcoin Core versions prior to 0.21.0 Description: The issue allows an attacker to prevent a node from seeing a specific unconfirmed transaction due to mishandled transaction re-requests. Recommendations: For versions prior to 0.21.0, update ...
CVE-2024-52914
Bitcoin Core versions prior to 0.18.0 are vulnerable to a denial of service (DoS) condition. A node can be stalled for hours when processing the orphans of a specially crafted unconfirmed transaction . The root cause is related to the allocation of resources without limits or throttling (CWE-770)...
PT-2024-35482
Name of the Vulnerable Software and Affected Versions: Bitcoin Core versions prior to 0.18.0 Description: A node could be stalled for hours when processing the orphans of a crafted unconfirmed transaction. This issue affects Bitcoin Core and can lead to a denial of service. Recommendations: For...
CVE-2024-52914
In Bitcoin Core before 0.18.0, a node could be stalled for hours when processing the orphans of a crafted unconfirmed transaction...
CVE-2024-52913: Allocation of Resources Without Limits or Throttling
In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled...