CVE-2021-44228 - log4j - Discourse anfällig?

[a.harper (Adrian Harper)]

Hi all

Is the vulnerable log4j library in use by Discourse - can an employee please issue a statement on potential exposure/review.

Thanks

[Falco]

Log4J is a Java library. Discourse is written in Ruby, not Java.

[a.harper (Adrian Harper)]

Thanks, so from the hosting side of things there is no Apache and log4j there?

[david (David Taylor)]

Correct, a standard installation of Discourse doesn’t use Apache.

[RGJ (Richard - Communiteq)]

Note that any self-hosted or non-standard Discourse installs running on Apache httpd are not affected either.

The Apache HTTP server project does not use the Apache Log4J library, they are both projects from the Apache foundation so they share a name, but that’s about it.

[VirgilVulpes]

Should those of us who run Discourse instances with java-based plugins disable said plugins?
(I’m definitely not a software engineer. That’s all Greek to me)

[merefield (Robert)]

Discourse Plugins are written in Ruby (on Rails) and Javascript (with Ember), so I’m not sure which plugins you are referring too?

NB Javascript and Java are not the same thing.

[david (David Taylor)]

Discourse and the Log4j vulnerability

On 9th December, CVE 2021-44228 was published for log4j, a commonly-used Java logging library. Subsequently, CVE-2021-45046 and CVE-2021-45105 have also been published. We’ve received a number of questions about these vulnerabilities, and whether they affect Discourse. Discourse is a Ruby application, and therefore does not make any use of this Java library. In addition, our standard installation instructions for self-hosted installations do not include any Java components. Managed discourse.…