Menu

Star on GitHub · 3.2k

CVE-2008-2573

8.5 · HIGH

Stack-based buffer overflow in SFTP in freeSSHd 1.2.1 allows remote authenticated users to execute arbitrary code via a long directory name in an SSH_FXP_OPENDIR (aka opendir) command.

Published Jun 6, 2008freesshdCWE-119EPSS 5.61%

Overview

CVE-2008-2573 is a high-severity vulnerability affecting freesshd freesshd. It was published on June 6, 2008 and has a CVSS 2.0 base score of 8.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 8.5, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

Stack-based buffer overflow in SFTP in freeSSHd 1.2.1 allows remote authenticated users to execute arbitrary code via a long directory name in an SSH_FXP_OPENDIR (aka opendir) command.

Remediation

Check the references section for vendor advisories and patches from freesshd. Update freesshd to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2008-2573?

CVE-2008-2573 is a high-severity vulnerability affecting freesshd freesshd. It was published on June 6, 2008 and has a CVSS 2.0 base score of 8.5 (HIGH).

How severe is CVE-2008-2573?

This vulnerability has a CVSS 2.0 base score of 8.5, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2008-2573?

Check the references section for vendor advisories and patches from freesshd. Update freesshd to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2008-2573?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2008-2573 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2008

View all