Great Circle Associates Firewalls
(January 1996)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: [ssh] the other bug I mentioned (part 5/5)
From: Brain21 <brain21 @ montag33 . residence . gatech . edu>
Date: Mon, 22 Jan 1996 14:27:54 -0500 (EST)
To: firewalls @ greatcircle . com

| Date: Thu, 18 Jan 96 17:35:12 EST
| From: Barry Jaspan <bjaspan @
 bbnplanet .
 com>
| Subject: the other bug I mentioned
| 
| 
| I mentioned in a previous message that I had found another bug in SSH.
| Here it is:
| 
|   /* Now that we are back to our own permissions, create ~/.ssh directory
|      if it doesn\'t already exist. */
|   sprintf(buf, "%s/%s", pw->pw_dir, SSH_USER_DIR);
| 
| The program does not perform bounds checking on pw->pw_dir.  In an NIS
| environment, an attacker could forge an NIS response with an overly
| long homedir and overwrite the buffer.  The simple way to exploit this
| bug would be to send garbage data, causing ssh to coredump and reveal
| the host's key (as in my previous attack).  A more insidous attack
| would be to send a homedir string that contained executable code that,
| say, instructed ssh to mail the USER'S private key to the attacker
| elsewhere on the network, and then allow ssh to continue running.
| 
| This is the same form of attack that the Morris internet worm used on
| November 2, 1988.
| 
| This is obviously much harder to exploit, but also more dangerous.
| Luckily, it is also easy to fix. :-)
| 
| Barry
| 

Indexed By Date Previous: Re: Security bug in ssh.c (1.2.0) (part 4/5)
From: Brain21 <brain21 @ montag33 . residence . gatech . edu>
Next: Re: Product selection
From: Rick Smith <smith @ sctc . com>
Indexed By Thread Previous: Re: Security bug in ssh.c (1.2.0) (part 4/5)
From: Brain21 <brain21 @ montag33 . residence . gatech . edu>
Next: M$ security problem
From: Kent Dahlgren <kent @ trouble . WV . TEK . COM>

Google
 
Search Internet Search www.greatcircle.com