Log4j and log4j2 library vulnerability
-
I am aware of solr being detected by the static analyzers (the marketplace images complain about the same). solr is used internally for full text search in the mail container. It's not on by default and it's also not exposed outside the internal docker network (so not exposed to outside world).
Still, we will update the mail container. Solr only put out a new release yesterday which update log4j.
-
I am aware of solr being detected by the static analyzers (the marketplace images complain about the same). solr is used internally for full text search in the mail container. It's not on by default and it's also not exposed outside the internal docker network (so not exposed to outside world).
Still, we will update the mail container. Solr only put out a new release yesterday which update log4j.
@girish min patch to rectify log4j2 issues is 2.16 .. 2.15 is affected by cvss 9.0 rce in some instances.
-
Docker Scan should allow us to scan cloudron containers if any doubt remains :
https://www.docker.com/blog/apache-log4j-2-cve-2021-44228/edit : https://github.com/docker/scan-cli-plugin/releases/tag/v0.11.0
@rmdes good suggestion.
-
@rmdes good suggestion.
@mastadamus I'm happy to report that Crowdsec successfully responded to a log4j exploit scanner. If you set up your nginx log configuration per my post in support, and install the nginx collection as well as the log4j2 collection with an firewall iptable bouncer it will auto block any ip belonging to an attempt it parses out.
crowdsec crowdsecurity/apache_log4j2_cve-2021-44228 Ip 45.83.65.33 2021-12-17 07:55:25 2021-12-17 07:55:25
-
@mastadamus I'm happy to report that Crowdsec successfully responded to a log4j exploit scanner. If you set up your nginx log configuration per my post in support, and install the nginx collection as well as the log4j2 collection with an firewall iptable bouncer it will auto block any ip belonging to an attempt it parses out.
crowdsec crowdsecurity/apache_log4j2_cve-2021-44228 Ip 45.83.65.33 2021-12-17 07:55:25 2021-12-17 07:55:25
@mastadamus do you have a step by step instructions to setup crowdsec in a cloudron context ?
-
@mastadamus do you have a step by step instructions to setup crowdsec in a cloudron context ?
@rmdes I'll put one together later tonight.
-
@mastadamus do you have a step by step instructions to setup crowdsec in a cloudron context ?
-
@mastadamus thanks alot, will try to implement this & will report under your post
-
@necrevistonnezr ah ok, then this is fine. It is not exposed or anything.
@nebulon I found log4j2 libary usage in kutt (urlshortener)
Standard config:
# ONLY NEEDED FOR MIGRATION !!1! # Neo4j database credential details NEO4J_DB_URI=bolt://localhost NEO4J_DB_USERNAME= NEO4J_DB_PASSWORD=changed to this without errors:
# ONLY NEEDED FOR MIGRATION !!1! # Neo4j database credential details #NEO4J_DB_URI=bolt://localhost #NEO4J_DB_USERNAME=neo4j #NEO4J_DB_PASSWORD=BjEphmupAf1D5pDDIs there anything else to do?
Is that even a issue? -
@nebulon I found log4j2 libary usage in kutt (urlshortener)
Standard config:
# ONLY NEEDED FOR MIGRATION !!1! # Neo4j database credential details NEO4J_DB_URI=bolt://localhost NEO4J_DB_USERNAME= NEO4J_DB_PASSWORD=changed to this without errors:
# ONLY NEEDED FOR MIGRATION !!1! # Neo4j database credential details #NEO4J_DB_URI=bolt://localhost #NEO4J_DB_USERNAME=neo4j #NEO4J_DB_PASSWORD=BjEphmupAf1D5pDDIs there anything else to do?
Is that even a issue? -
@3gal neo4j and log4j are different. the former is a database and the latter is logging library. Kutt anyway is written in typescript and not affected by log4j issue.
