Skip to content
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

Log4J Vulnerability Question #41191

Closed
ASH-Anthony opened this issue Dec 15, 2021 · 3 comments
Closed

Log4J Vulnerability Question #41191

ASH-Anthony opened this issue Dec 15, 2021 · 3 comments
Labels
question Issues that look for answers.

Comments

@ASH-Anthony
Copy link

Apologies that this isn't a feature request and there isn't a template for a general question. I know this is probably a silly question for this package, but we need to assess our entire toolchain for any potential Log4J vulnerabilities related to CVE-2021-44228. Is Node vulnerable to this vulnerability?

@ASH-Anthony ASH-Anthony added the feature request Issues that request new features to be added to Node.js. label Dec 15, 2021
@Trott
Copy link
Member

Trott commented Dec 15, 2021

Is Node vulnerable to this vulnerability?

No.

@Trott Trott closed this as completed Dec 15, 2021
@richardlau richardlau added question Issues that look for answers. and removed feature request Issues that request new features to be added to Node.js. labels Dec 15, 2021
@hp8wvvvgnj6asjm7
Copy link

hp8wvvvgnj6asjm7 commented Dec 16, 2021

maybe winston and pino are :octocat:

@Trott
Copy link
Member

Trott commented Dec 16, 2021

maybe winston and pino are :octocat:

No and no. The Log4J vulnerability is a Java vulnerability.

I'm locking this issue.

@nodejs nodejs locked as off-topic and limited conversation to collaborators Dec 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Issues that look for answers.
Projects
None yet
Development

No branches or pull requests

4 participants