Skip to content

Conversation

@kasicka
Copy link

@kasicka kasicka commented Jun 24, 2017

CVE: CVE-2017-1000381
Upstream bug: https://c-ares.haxx.se/adv_20170620.html
Upstream patch: https://c-ares.haxx.se/CVE-2017-1000381.patch

I haven't seen PR/issue for this CVE, so I created one. It's the same as upstream c-ares patch.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

bundled c-ares

@nodejs-github-bot nodejs-github-bot added the cares Issues and PRs related to the c-ares dependency or the cares_wrap binding. label Jun 24, 2017
@XadillaX
Copy link
Contributor

XadillaX commented Jun 24, 2017

when will cares release the new version? how about updating to 1.13 directly?

@kasicka
Copy link
Author

kasicka commented Jun 24, 2017

how about updating to 1.13 directly?

Maybe in master/v8.x, but is it really an option for v6.x and v4.x?

@bnoordhuis
Copy link
Member

I didn't see any backwards compatibility concerns in the 1.12..1.13 diff. I'm good with upgrading wholesale in all release branches.

@kasicka
Copy link
Author

kasicka commented Jun 24, 2017

Consider this just an issue then.

@MylesBorins
Copy link
Contributor

This has landed in all active release lines

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cares Issues and PRs related to the c-ares dependency or the cares_wrap binding.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants