Logo! Soft Comfort
Approved changes feed: RSS · Atom
cpe:2.3:a:siemens:logo\!_soft_comfort:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Siemens (4bd2a91b-02ad-5c3d-b25f-70697e0c9d7f) |
|---|---|
| Product | Logo! Soft Comfort (4caad27e-9927-5b8e-87b3-b10e13f3699a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-45046 |
vulnerable | 2026-06-08 05:36:47.736604 |
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-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.
Published: 2021-12-14T16:55:09.000Z
Updated: 2025-10-21T23:25:22.768Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-44228 |
vulnerable | 2026-06-08 05:36:45.222493 |
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 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.
Published: 2021-12-10T00:00:00.000Z
Updated: 2025-10-21T23:25:23.121Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-25244 |
vulnerable | 2026-06-08 05:22:36.639376 |
Details available
HIGH (8.4)
A vulnerability has been identified in LOGO! Soft Comfort (All versions < V8.4). The software insecurely loads libraries which makes it vulnerable to DLL hijacking.
Successful exploitation by a local attacker could lead to a takeover of the system
where the software is installed.
Published: 2021-04-22T20:42:19.000Z
Updated: 2024-08-04T15:33:05.434Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-25243 |
vulnerable | 2026-06-08 05:22:36.638915 |
Details available
MEDIUM (5.1)
A vulnerability has been identified in LOGO! Soft Comfort (All versions < V8.4). A zip slip vulnerability could be triggered while importing a compromised project file
to the affected software. Chained with other vulnerabilities this vulnerability could
ultimately lead to a system takeover by an attacker.
Published: 2021-04-22T20:42:19.000Z
Updated: 2024-11-19T15:01:36.881Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-25231 |
vulnerable | 2026-06-08 05:22:36.585818 |
Details available
A vulnerability has been identified in LOGO! 8 BM (incl. SIPLUS variants) (All versions < V8.3), LOGO! Soft Comfort (All versions < V8.3). The encryption of program data for the affected devices uses a static key. An attacker could use this key to extract confidential information from protected program files.
Published: 2020-12-14T21:05:18.000Z
Updated: 2024-08-04T15:33:05.447Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-10924 |
vulnerable | 2026-06-08 05:12:25.684794 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-12740 |
vulnerable | 2026-06-08 05:08:47.726258 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.