Summary
Apache Log4j is used for logging events in WAGO Smart Script in Version 4.2 and higher. Events logged by Log4j can contain JNDI references. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. Additionally, Log4j does not protect from self-referential lookups, which can lead to Denial of Service.
UPDATE A1/2:
Affected versions:
CVE-2021-44228 and CVE-2021-45046:
WAGO Smart Script >= Version 4.2 and < Version 4.8.1.3
CVE-2021-45105:
WAGO Smart Script >= Version 4.2 and < Version 4.8.1.4
CVE-2021-44832
WAGO Smart Script >= Version 4.2 and < Version 4.8.1.5
END UPDATE A1/2
Details
Impact
Log Messages controlled by an attacker could lead to remote code execution. Additionally, Log4j does not protect from self-referential lookups, which can lead to Denial of Service.
Mitigation
Do not use projects from untrusted sources.
For further impact information and risk mitigation, see the recommendations of the
Apache Foundation https://logging.apache.org/log4j/2.x/security.html
Bundesamt für Sicherheit in der Informationstechnik (BSI) https://www.bsi.bund.de/DE/Service-Navi/Presse/Pressemitteilungen/Presse2021/211211_log4Shell_WarnstufeRot.html
Remediation
UPDATE A2/2:Install Version 4.8.1.5 or later of WAGO Smart Script, which is available on our Website.Customers using Version 4.6 or higher can already use the integrated 'Check for update' function of WAGO Smart Script to update to Version 4.8.1.5.END UPDATE A2/2
Vulnerabilities 4
-
Critical 10.0
Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints
Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who …
KEV Dec 10, 2021 -
Critical 9.0
Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attack
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-defaul…
KEV May 1, 2023 -
Medium 6.6
Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control o…
-
Medium 5.9
Apache Log4j2 does not always protect from infinite recursion in lookup evaluation
Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a craf…
Revision history
-
#3
Fix: added distribution, quotation mark
-
#2
Update
-
#1
Initial revision.
References
-
WAGO advisory overview at CERT@VDE
https://certvde.com/de/advisories/vendor/wago/
-
VDE-2021-060: WAGO: Smart Script affected by Log4Shell Vulnerability - HTML
https://certvde.com/en/advisories/VDE-2021-060