FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The VUXML data was last processed by FreshPorts on 2024-11-16 12:24:49 UTC

List all Vulnerabilities, by package

List all Vulnerabilities, by date

k68

These are the vulnerabilities relating to the commit you have selected:

VuXML ID	Description
3fadd7e4-f8fb-45a0-a218-8fd6423c338f	graylog -- include log4j patches Apache Software Foundation repos: Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or paramters can execute arbitrary code from attacker-controller LDAP servers when message lookup substitution is enabled. Discovery 2021-12-10 Entry 2021-12-11 graylog < 4.2.3 CVE-2021-44228 https://github.com/Graylog2/graylog2-server/commit/d3e441f1126f0dc292e986879039a87c59375b2a https://logging.apache.org/log4j/2.x/security.html
650734b2-7665-4170-9a0a-eeced5e10a5e	graylog -- remote code execution in log4j from user-controlled log input Apache Software Foundation reports: It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a denial of service (DOS) attack. Log4j 2.15.0 makes a best-effort attempt to restrict JNDI LDAP lookups to localhost by default. Log4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. Discovery 2021-11-14 Entry 2021-12-17 graylog < 4.2.4 CVE-2021-45046 https://github.com/Graylog2/graylog2-server/commit/d3e441f https://github.com/Graylog2/graylog2-server/commit/dd24b85 https://logging.apache.org/log4j/2.x/security.html

VuXML ID

Description

3fadd7e4-f8fb-45a0-a218-8fd6423c338f

graylog -- include log4j patches

Apache Software Foundation repos:

Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or paramters can execute arbitrary code from attacker-controller LDAP servers when message lookup substitution is enabled.

Discovery 2021-12-10
Entry 2021-12-11
graylog

< 4.2.3

CVE-2021-44228
https://github.com/Graylog2/graylog2-server/commit/d3e441f1126f0dc292e986879039a87c59375b2a
https://logging.apache.org/log4j/2.x/security.html

650734b2-7665-4170-9a0a-eeced5e10a5e

graylog -- remote code execution in log4j from user-controlled log input

Apache Software Foundation reports:

It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a denial of service (DOS) attack. Log4j 2.15.0 makes a best-effort attempt to restrict JNDI LDAP lookups to localhost by default. Log4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default.

Discovery 2021-11-14
Entry 2021-12-17
graylog

< 4.2.4

CVE-2021-45046
https://github.com/Graylog2/graylog2-server/commit/d3e441f
https://github.com/Graylog2/graylog2-server/commit/dd24b85
https://logging.apache.org/log4j/2.x/security.html