Bug#801530: openssh-client: Segfault on malformed keys - possible security impact)

To: 801530@bugs.debian.org
Subject: Bug#801530: openssh-client: Segfault on malformed keys - possible security impact)
From: Steve Kemp <steve@steve.org.uk>
Date: Mon, 12 Oct 2015 19:14:32 +0000
Message-id: <[🔎] 20151012191432.GA32553@steve.org.uk>
Reply-to: Steve Kemp <steve@steve.org.uk>, 801530@bugs.debian.org
In-reply-to: <handler.801530.B801530.144464087814327.ackinfo@bugs.debian.org>
References: <[🔎] 20151012090750.GA30280@steve.org.uk> <handler.801530.B801530.144464087814327.ackinfo@bugs.debian.org>

> .. and the exciting-looking address is apparently a typical load address
> for the ssh binary.

  Yes.  It was in the ascii-range, which made me more optimistic.

  (I'm too used to using AAA..AAA as input and seeing 0x41. 0x55 looks
 close enough to be plausible.)

Steve
--

Reply to:

References:
- Bug#801530: openssh-client: Segfault on malformed keys - possible security impact
  - From: Steve Kemp <steve@steve.org.uk>

Prev by Date: Bug#801530: segfault is null-pointer dereference
Next by Date: Bug#774711: recommendations for changing openssh defaults
Previous by thread: Bug#801530: openssh-client: Segfault on malformed keys - possible security impact
Next by thread: Bug#801530: openssh-client: Segfault on malformed keys - possible security impact
Index(es):
- Date
- Thread