The c-ares function `ares_parse_naptr_reply()`, which is used for parsing NAPTR responses, could be triggered to read memory outside of the given input buffer if the passed in DNS response packet was crafted in a particular way. External References: https://c-ares.haxx.se/adv_20170620.html
Acknowledgments: Name: Daniel Stenberg Upstream: LCatro
Created mingw-c-ares tracking bugs for this issue: Affects: epel-7 [bug 1463133] Affects: fedora-all [bug 1463135] Created nodejs tracking bugs for this issue: Affects: epel-all [bug 1463134] Affects: fedora-all [bug 1463137] Affects: openshift-1 [bug 1463136]
Patch: https://c-ares.haxx.se/CVE-2017-1000381.patch
That's two CVE's (this and CVE-2016-5180 in #BZ1387961) applicable to c-ares in EL6. Will this patch be backported, or can the version be rebased?
Upstream commit that was applied in 1.13.0: https://github.com/c-ares/c-ares/commit/9478908a490a6bf009ba58d81de8c1d06d50a117 The above fix introduce a regression that was fixed in 1.14.0: https://github.com/c-ares/c-ares/commit/18ea99693d63f957ecb670045adbd2c1da8a4641
c-ares version bundled in NodeJS was fixed in NodeJS versions 4.8.4, 6.11.1, 7.10.1, and 8.1.4: https://nodejs.org/en/blog/vulnerability/july-2017-security-releases/ https://nodejs.org/en/blog/release/v4.8.4/ https://nodejs.org/en/blog/release/v6.11.1/ https://nodejs.org/en/blog/release/v7.10.1/ https://nodejs.org/en/blog/release/v8.1.4/
The rh-nodejs6-nodejs packages in Red Hat Software Collections got this problem corrected when they were rebased from version 6.9.1 to 6.11.3 via RHSA-2017:2908: https://access.redhat.com/errata/RHSA-2017:2908 The rh-nodejs8-nodejs packages in Red Hat Software Collections were first released based on fixed upstream version 8.6.0 and hence were never affected by this issue.