Vulnerability Note VU#758054

Reflection for Secure IT Windows Server 6.0 changed case sensitivity of allow and deny lists

Original Release date: 31 Aug 2005 | Last revised: 01 Sep 2005

Overview

Reflection for Secure IT Windows Server version 6.0 uses different case-sensitivity in evaluating the allow and deny lists as previous versions, potentionally allowing unintended access.

Description

Reflection for Secure IT Windows Server version 6.0, an SSH server from WRQ formerly known as F-Secure SSH server, provides allow and deny lists of regular expressions to configure the set of accounts that should be able to access the host. Prior to 6.0, these regular expressions were evaluated in a case-insensitive manner. In 6.0, the regular expressions are evaluated in a case-sensitive manner, potentionally allowing an attacker to login to previously-denied accounts.

Impact

A remote attacker may be able to login to previously-denied accounts, if the attacker can authenticate to the account (e.g., he knows the account's password).

Solution

Upgrade

According to WRQ, version 6.0, build 24 of Reflection for Secure IT Windows Server evaluates allow and deny strings in a case-insensitive manner. This restores the prior behavior, but may result in usernames matching the allow list that did not match in prior builds of version 6.0.


Manually Create Expressions

Enter regular expressions that match all case-combinations of the desired strings.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
WRQ, Inc.Affected-30 Aug 2005
F-Secure CorporationNot Affected-28 Jul 2005
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A

References

Credit

Thanks to WRQ for reporting this issue.

This document was written by Hal Burch.

Other Information

  • CVE IDs: Unknown
  • Date Public: 25 Aug 2005
  • Date First Published: 31 Aug 2005
  • Date Last Updated: 01 Sep 2005
  • Severity Metric: 1.01
  • Document Revision: 22

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.