What is the severity of CVE-2005-2770?

CVE-2005-2770 is considered a medium severity vulnerability due to its potential for unauthorized access.

How do I fix CVE-2005-2770?

To fix CVE-2005-2770, ensure that SSH key authentication is configured under accounts that have not been renamed.

What does CVE-2005-2770 exploit?

CVE-2005-2770 exploits the improper handling of renamed Windows Administrator or Guest accounts in SSH key authentication.

Who is affected by CVE-2005-2770?

CVE-2005-2770 affects users of WRQ Reflection for Secure IT Windows Server version 6.0.

What are the potential consequences of CVE-2005-2770?

The potential consequences of CVE-2005-2770 include unauthorized remote access using original account names.

Vulnerability/
CVE-2005-2770

high

7.5

CWE

NVD-CWE-Other

2/9/2005

7/8/2024

CVE-2005-2770

First published: Fri Sep 02 2005(Updated: )

WRQ Reflection for Secure IT Windows Server 6.0 (formerly known as F-Secure SSH server) does not properly handle when the Windows Administrator or Guest accounts are renamed after SSH key authentication has been configured, which allows remote attackers to use the original names during login.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Attachmate Reflection for Secure IT	=6.0

Remedy

http://secunia.com/advisories/16649/

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2005-2770?
CVE-2005-2770 is considered a medium severity vulnerability due to its potential for unauthorized access.
How do I fix CVE-2005-2770?
To fix CVE-2005-2770, ensure that SSH key authentication is configured under accounts that have not been renamed.
What does CVE-2005-2770 exploit?
CVE-2005-2770 exploits the improper handling of renamed Windows Administrator or Guest accounts in SSH key authentication.
Who is affected by CVE-2005-2770?
CVE-2005-2770 affects users of WRQ Reflection for Secure IT Windows Server version 6.0.
What are the potential consequences of CVE-2005-2770?
The potential consequences of CVE-2005-2770 include unauthorized remote access using original account names.

agent/type
agent/references
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/last-modified-date
agent/remedy
agent/author
agent/event
agent/first-publish-date
agent/description
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/wrq
canonical/attachmate reflection for secure it
version/attachmate reflection for secure it/6.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2005-2770?
CVE-2005-2770 is considered a medium severity vulnerability due to its potential for unauthorized access.
How do I fix CVE-2005-2770?
To fix CVE-2005-2770, ensure that SSH key authentication is configured under accounts that have not been renamed.
What does CVE-2005-2770 exploit?
CVE-2005-2770 exploits the improper handling of renamed Windows Administrator or Guest accounts in SSH key authentication.
Who is affected by CVE-2005-2770?
CVE-2005-2770 affects users of WRQ Reflection for Secure IT Windows Server version 6.0.
What are the potential consequences of CVE-2005-2770?
The potential consequences of CVE-2005-2770 include unauthorized remote access using original account names.