Vulnerabilidades do Siemens Logo! Soft Comfort
🔔 Criar alerta RSS Verificador de versão
CVEs publicadas que afetam Siemens Logo! Soft Comfort: 4 registro(s), com versões afetadas e correções.cpe:2.3:a:siemens:logo!_soft_comfort
CVE-2026-57263
Média · 6.8
CWE-759 11/08/2026
A vulnerability has been identified in LOGO! Soft Comfort (All versions < V9). The…
A vulnerability has been identified in LOGO! Soft Comfort (All versions < V9). The project password feature in the affected products stores the password as an unsalted SHA-256 hash. This could allow an attacker who has obtained the project file to perform efficient offline dictionary or brute-force attacks against the unsalted hash.
CVE-2026-57262
Média · 6.8
CWE-321 11/08/2026
A vulnerability has been identified in LOGO! Soft Comfort (All versions < V9). Affected…
A vulnerability has been identified in LOGO! Soft Comfort (All versions < V9). Affected products use a static, hardcoded AES master key to encrypt project files. This could allow a local attacker to extract the master key from the application files or memory and use it to decrypt project files or remove project passwords entirely without knowing the actual user-defined password.
CVE-2021-45046
Crítica · 9.0
KEV Urgente · 90 Exploit público Ransomware CWE-917 14/12/2021
Apache Log4j2 Deserialization of Untrusted Data Vulnerability
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 an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.
CVE-2021-44228
Crítica · 10.0
KEV Urgente · 100 Exploit público Ransomware CWE-20 10/12/2021
Apache Log4j2 Remote Code Execution Vulnerability
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 can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.