Glibc

[taylormadearmy]

Hi All

Apologies if it is a stupid question... But are we susceptible to the glibc vulnerability?

http://arstechnica.com/security/201...zzying-number-of-apps-and-devices-vulnerable/

Thanks,
T

 

[CiscoX]

Hi All

Apologies if it is a stupid question... But are we susceptible to the glibc vulnerability?

http://arstechnica.com/security/201...zzying-number-of-apps-and-devices-vulnerable/

Thanks,
T

Hi,
Duplicate

http://www.snbforums.com/threads/ex...ber-of-software-and-devices-vulnerable.30488/

 

[taylormadearmy]

Hi,
Duplicate

http://www.snbforums.com/threads/ex...ber-of-software-and-devices-vulnerable.30488/

*Embarrassed face* Thanks - I did search - honest! No idea how I missed that!

 

[ASAT]

Just to be safe, I applied the patch to my Entware-ng toolchain and recompiled all the packages.

[PATCH] CVE-2015-7547 --- glibc getaddrinfo() stack-based buffer overflow


-

 

[kvic]

Just to be safe, I applied the patch to my Entware-ng toolchain and recompiled all the packages.

[PATCH] CVE-2015-7547 --- glibc getaddrinfo() stack-based buffer overflow


-

I'm wondering if @zyxmon is on top of this...

EDIT: corrected typo

 

[zyxmon]

We will switch to gcc 5.3.0 to add GO 1.4.2 (through) gccgo support in the nearest time.
As for glibc - I'll add CVE patches to 2.22 or move to 2.23

 

[zyxmon]

CVE patches for glibc 2.22 and glibc 2.23 (as a choice) are in the repo (go53 branch):
https://github.com/Entware-ng/Entware-ng/commit/c00cb12b4100cf1bfc997e71030719338baddb6f
https://github.com/Entware-ng/Entware-ng/commit/56ffa7ecd96d4beb9c21624002d5ba69cd3ef85e