Skip to content
Fencer Intel
critical 9.8

CVE-2020-7593 json

A vulnerability has been identified in LOGO!

published 6y ago modified 4mo ago also EUVD-2020-28718

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
8.7%
EPSS 8.7% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

A vulnerability has been identified in LOGO! 8 BM (incl. SIPLUS variants) (V1.81.01 - V1.81.03), LOGO! 8 BM (incl. SIPLUS variants) (V1.82.01), LOGO! 8 BM (incl. SIPLUS variants) (V1.82.02). A buffer overflow vulnerability exists in the Web Server functionality of the device. A remote unauthenticated attacker could send a specially crafted HTTP request to cause a memory corruption, potentially resulting in remote code execution.

Is CVE-2020-7593 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-20-196-08 updated cvss 9.8

Siemens LOGO! Web Server

  • Siemens LOGO! 8 BM (incl.'SIPLUS variants) >=V1.81.01, <=V1.81.03, V1.82.01, V1.82.02
    affected: fixed in V1.81.04, mitigation

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

Exploit prediction

8.72% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • talosintelligence.com https://www.talosintelligence.com/vulnerability_reports/TALOS-2020-1069 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • Siemens AG LOGO! 8 BM (incl. SIPLUS variants)

Classification

Weakness
  • CWE-120 Buffer Copy without Checking Size of Input

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.