Menu

Star on GitHub · 3.2k

CVE-2005-4310

7.5 · HIGH

SSH Tectia Server 5.0.0 (A, F, and T), when allowing host-based authentication only, allows users to log in with the wrong credentials.

Published Dec 17, 2005sshEPSS 1.40%

Overview

CVE-2005-4310 is a high-severity vulnerability affecting ssh tectia_server. It was published on December 17, 2005 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

SSH Tectia Server 5.0.0 (A, F, and T), when allowing host-based authentication only, allows users to log in with the wrong credentials.

Remediation

Check the references section for vendor advisories and patches from ssh. Update tectia_server 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-2005-4310?

CVE-2005-4310 is a high-severity vulnerability affecting ssh tectia_server. It was published on December 17, 2005 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2005-4310?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2005-4310?

Check the references section for vendor advisories and patches from ssh. Update tectia_server 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-2005-4310?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2005-4310 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 2005

View all