Skip to content

Heads up of Node.js security releases 14 Feb 2023 #1843

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mhdawson opened this issue Feb 7, 2023 · 7 comments · Fixed by #1846 or #1849
Closed

Heads up of Node.js security releases 14 Feb 2023 #1843

mhdawson opened this issue Feb 7, 2023 · 7 comments · Fixed by #1846 or #1849

Comments

@mhdawson
Copy link
Member

mhdawson commented Feb 7, 2023

As per the Node.js security release process this is the FYI that there is going to be a security release 14 Feb 2023

@tomymehdi
Copy link

Hello @mhdawson. This would address CVE-2023-0286 (https://avd.aquasec.com/nvd/cve-2023-0286) on alpine images with tag 19-alpine3.16 ?

@nschonni
Copy link
Member

nschonni commented Feb 8, 2023

https://nodejs.org/en/blog/vulnerability/february-2023-security-releases/

@mhdawson
Copy link
Member Author

Security releases are now out and should be ready for intergration into containers.

@SimenB SimenB linked a pull request Feb 17, 2023 that will close this issue
@SimenB
Copy link
Member

SimenB commented Feb 17, 2023

Ooops, linked PR is missing Node 18 for alpine. From what I can see it is built, but not available.

https://unofficial-builds.nodejs.org/logs/202302170648-v18.14.1/ shows musl as done
https://unofficial-builds.nodejs.org/download/release/v18.14.1/ is completely empty

/cc @nodejs/build

EDIT: arm build is still going, maybe the files aren't updated until all builds are completed? musl, which is the one we're waiting for, completed 30 minutes ago.

@nschonni
Copy link
Member

EDIT: arm build is still going, maybe the files aren't updated until all builds are completed? musl, which is the one we're waiting for, completed 30 minutes ago.

nodejs/unofficial-builds#22

I'm not sure why the bot opened the PR when the 18 musl builds weren't ready. It's supposed to fail till they are all ready

@SimenB
Copy link
Member

SimenB commented Feb 17, 2023

Ok, finally done now. Hopefully the bot picks it up as I cannot run the update script on my current machine (#1848)

@SimenB SimenB linked a pull request Feb 17, 2023 that will close this issue
@SimenB
Copy link
Member

SimenB commented Feb 17, 2023

It's supposed to fail till they are all ready

Yeah, good point...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants