Keep Track of the Latest Vulnerabilities
with SecurityTracker!
    Home    |    View Topics    |    Search    |    Contact Us    |   


Sign Up
Sign Up for Your FREE Weekly SecurityTracker E-mail Alert Summary
Instant Alerts
Buy our Premium Vulnerability Notification Service to receive customized, instant alerts
Put SecurityTracker Vulnerability Alerts on Your Web Site -- It's Free!
Become a Partner and License Our Database or Notification Service
Report a Bug
Report a vulnerability that you have found to SecurityTracker

Category:   Application (VPN)  >   SSH Tectia Server Vendors:   SSH Communications
SSH Tectia Server Insecure File Permissions May Let Local Users Gain Elevated Privileges
SecurityTracker Alert ID:  1017913
SecurityTracker URL:
CVE Reference:   CVE-2007-2063   (Links to External Site)
Updated:  May 14 2008
Original Entry Date:  Apr 16 2007
Impact:   User access via local system
Fix Available:  Yes  Vendor Confirmed:  Yes  
Version(s): prior to 5.4.0
Description:   A vulnerability was reported in SSH Tectia Server. A local user may be able to obtain elevated privileges on the target system.

The SSH Tectia Server may be run as a started task with an empty umask on some z/OS installations. As a result, some HFS files may be created with world-writable permissions.

A local user may be able to exploit this to gain elevated privileges.

Impact:   A local user can obtain elevated privileges on the target system.
Solution:   The vendor has issued a fixed version (5.4.0).

The SSH advisory is available at:

Vendor URL: (Links to External Site)
Cause:   Access control error
Underlying OS:   z/OS

Message History:   None.

 Source Message Contents

Date:  Mon, 16 Apr 2007 10:29:53 -0400
Subject:  Release Notes for SSH Tectia Server 5.4.0 for IBM z/OS

  - Server creates world-writable directories.
    On some z/OS installations the server could be run as a started task 
    with an empty umask, which caused some created HFS files to have 
    insecure (world-writable) permissions.
    If upgrading to this release, you must verify that the environment file
    used by your sshd2 started task script (originally called SSHENV in the
    SAMPLES directory) contains an appropriate _BPX_BATCH_UMASK declaration.

Go to the Top of This SecurityTracker Archive Page

Home   |    View Topics   |    Search   |    Contact Us

Copyright 2015, LLC