CVE-2006-4924

CVE-2006-4924 is a high-severity vulnerability in Openbsd Openssh with a CVSS 2.0 base score of 7.8. Its EPSS exploit-prediction score of 35% places it in the 98th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-399.

Key facts

Description

sshd in OpenSSH before 4.4, when using the version 1 SSH protocol, allows remote attackers to cause a denial of service (CPU consumption) via an SSH packet that contains duplicate blocks, which is not properly handled by the CRC compensation attack detector.

Frequently asked questions

What is CVE-2006-4924?
sshd in OpenSSH before 4.4, when using the version 1 SSH protocol, allows remote attackers to cause a denial of service (CPU consumption) via an SSH packet that contains duplicate blocks, which is not properly handled by the CRC compensation attack detector.
How severe is CVE-2006-4924?
CVE-2006-4924 has a CVSS 2.0 base score of 7.8, rated high severity.
Is CVE-2006-4924 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 35% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-4924?
CVE-2006-4924 primarily affects Openbsd Openssh. In total, 56 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2006-4924?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2006-4924 published?
CVE-2006-4924 was published on 2006-09-27 and last updated on 2026-06-16.

References

Affected products (56)

More vulnerabilities in Openbsd Openssh

All CVEs affecting Openbsd Openssh →

Other CWE-399 (Resource Management Errors) vulnerabilities

Browse all CWE-399 (Resource Management Errors) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: