OT: looking for help remembering name/info about security bug

List overview All Threads
Download

newer

older

OT: looking for help remembering...

Plessy core memory

sieler＠allegro.com

10 Jan 2022 10 Jan '22

10:04 p.m.

Hi, I'm trying to remember the name (and some information about) a past security bug, for an article. Somewhere between 4 and 6 years ago (I think), there was a fairly major security bug reported (probably in Linux, or in SSH code, but something widely used). IIRC, the bug was a single line that called a function (possibly along the lines of CredentialsCheck), and may have involved a bit-wise or (or and) instead of a logical one. It may have been that either the routine wasn't getting called when it should, or that the programmer misinterpreted what the return value meant. Ring any bells? thanks! Stan

Show replies by date

lproven＠gmail.com

11 Jan 11 Jan

3:38 a.m.

On Tue, 11 Jan 2022 at 07:04, Stan Sieler via cctalk <cctalk at classiccmp.org> wrote:

...

Somewhere between 4 and 6 years ago (I think), there was a fairly major security bug reported (probably in Linux, or in SSH code, but something widely used).

Too vague. I think you need to narrow it down. Heartbleed, Spectre, Rowhammer, Meltdown, Shellshock? https://github.com/hannob/vulns -- Liam Proven ~ Profile: https://about.me/liamproven Email: lproven at cix.co.uk ~ gMail/gTalk/FB: lproven at gmail.com Twitter/LinkedIn: lproven ~ Skype: liamproven UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053

billdegnan＠gmail.com

4 a.m.

You're probably talking about the java bug from back then. I forget the name ofnit. Bill On Tue, Jan 11, 2022, 6:38 AM Liam Proven via cctalk <cctalk at classiccmp.org> wrote:

...

On Tue, 11 Jan 2022 at 07:04, Stan Sieler via cctalk <cctalk at classiccmp.org> wrote:

Somewhere between 4 and 6 years ago (I think), there was a fairly major security bug reported (probably in Linux, or in SSH code, but something widely used).

abs＠absd.org

7:20 a.m.

On Tue, 11 Jan 2022 at 06:04, Stan Sieler via cctalk <cctalk at classiccmp.org> wrote:

...

Just on the offchangce the bell might be named "Apple" (it's a goto fail rather than a bit-wise issue) https://nakedsecurity.sophos.com/2014/02/24/anatomy-of-a-goto-fail-apples-s… David

hauke＠Espresso.Rhein-Neckar.DE

10:26 a.m.

On Mon, 10 Jan 2022 22:04:33 -0800, Stan Sieler via cctalk wrote:

...

It may have been that either the routine wasn't getting called when it should, or that the programmer misinterpreted what the return value meant.

The Debian 4 OpenSSL disaster comes to mind, where IIRC a know-it-all package manager beautified the source and reduced the effective length of any generated keys to 32 bit. But that was more like 15 yrs ago... Cheerio, Hauke -- Hauke Fath <hauke at Espresso.Rhein-Neckar.DE> Linn?weg 7 64342 Seeheim-Jugenheim Germany

jon＠jonworld.com

12:02 p.m.

Heartbleed? On Tue, 11 Jan 2022 at 20:00, Hauke Fath via cctalk <cctalk at classiccmp.org> wrote:

...

On Mon, 10 Jan 2022 22:04:33 -0800, Stan Sieler via cctalk wrote:

It may have been that either the routine wasn't getting called when it should, or that the programmer misinterpreted what the return value

meant. The Debian 4 OpenSSL disaster comes to mind, where IIRC a know-it-all package manager beautified the source and reduced the effective length of any generated keys to 32 bit. But that was more like 15 yrs ago... Cheerio, Hauke -- Hauke Fath <hauke at Espresso.Rhein-Neckar.DE> Linn?weg 7 64342 Seeheim-Jugenheim Germany

-- -Jon +44 7792 149029

paulkoning＠comcast.net

12:11 p.m.

No, Heartbleed was a protocol specification error, where if you implemented what the spec said you automatically produced a security bug. paul

...

On Jan 11, 2022, at 3:02 PM, Jonathan Katz via cctalk <cctalk at classiccmp.org> wrote: Heartbleed? On Tue, 11 Jan 2022 at 20:00, Hauke Fath via cctalk <cctalk at classiccmp.org> wrote:

On Mon, 10 Jan 2022 22:04:33 -0800, Stan Sieler via cctalk wrote:

It may have been that either the routine wasn't getting called when it should, or that the programmer misinterpreted what the return value

-- -Jon +44 7792 149029

sieler＠allegro.com

6:06 p.m.

Re: On Tue, Jan 11, 2022 at 12:02 PM Jonathan Katz <jon at jonworld.com> wrote:

...

Heartbleed?

Checked the source code for that just now ... nope, sorry. I recall the problem being completely different from buffer overflow (e.g., by a unchecked memcpy ()), and more akin to either the programmer misinterpreting what a function did because of a poor name for the function, or using logical instead of boolean (or vice versa) logic. Of course, I could be wrong there :) thanks!