Siemens Intel Active Management Technology of SIMATIC IPCs
As a general security measure, Siemens strongly recommends to protect network access to devices with appropriate mechanisms. In order to operate the devices in a protected IT environment, Siemens recommends to configure the environment according to Siemens' operational guidelines for Industrial Security (Download: https://www.siemens.com/cert/operational-guidelines-industrial-security), and to follow the recommendations in the product manuals.
beschreibt (3)
Zugehörige CVEs.
| ID | Schweregrad | ausnutzbar | ||
|---|---|---|---|---|
| CVE-2018-3658US | medium5.3 | — | ||
Multiple memory leaks in Intel AMT in Intel CSME firmware versions before 12.0.5 may allow an unauthenticated user with Intel AMT provisioned to potentially cause a partial denial… | ||||
| CVE-2018-3657US | medium6.7 | — | ||
Multiple buffer overflows in Intel AMT in Intel CSME firmware versions before version 12.0.5 may allow a privileged user to potentially execute arbitrary code with Intel AMT execut… | ||||
| CVE-2018-3616US | medium5.9OT erhöht | — | ||
Bleichenbacher-style side channel vulnerability in TLS implementation in Intel Active Management Technology before 12.0.5 may allow an unauthenticated user to potentially obtain th… | ||||
Referenzen
Externe Belege — Patches, Meldungen, Analysen.
- SSA-377318: Multiple vulnerabilities in Intel Active Management Technology (AMT) of SIMATIC IPCs - HTML Versionself
- ICS Advisory ICSA-19-043-05 JSONself
- Recommended Practicesexternal
- ICS Advisory ICSA-19-043-05 - Web Versionself
- Recommended Practicesexternal
- Recommended Practicesexternal
- Recommended Practicesexternal
- Recommended Practicesexternal
Behebungen (66)
- MitigationSIMATIC FieldPG M5
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC FieldPG M5
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC FieldPG M5
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC427E (incl. SIPLUS variants)
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC427E (incl. SIPLUS variants)
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC427E (incl. SIPLUS variants)
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC477E
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC477E
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC477E
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC547E
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC547E
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC547E
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC547G
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC547G
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC547G
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC627D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC627D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC627D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC647D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC647D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC647D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC677D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC677D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC677D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC827D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC827D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC827D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC847D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC847D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC IPC847D
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC ITP1000
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC ITP1000
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- MitigationSIMATIC ITP1000
As a prerequisite for an attack, an attacker must be able to run malicious code on affected systems. Therefore, Siemens recommends determining if it is possible that untrusted code can be run on these systems, or if existing measures implemented by the operator reduce the likelihood of untrusted code being run.
- BehobenSIMATIC FieldPG M5
Update to V22.01.06 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC FieldPG M5
Update to V22.01.06 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC FieldPG M5
Update to V22.01.06 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC427E (incl. SIPLUS variants)
Update to V21.01.09 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC427E (incl. SIPLUS variants)
Update to V21.01.09 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC427E (incl. SIPLUS variants)
Update to V21.01.09 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC477E
Update to V21.01.09 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC477E
Update to V21.01.09 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC477E
Update to V21.01.09 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC547E
Update to R1.30.0 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC547E
Update to R1.30.0 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC547E
Update to R1.30.0 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC547G
Update to R1.23.0 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC547G
Update to R1.23.0 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC547G
Update to R1.23.0 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC627D
Update to V19.02.11 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC627D
Update to V19.02.11 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC627D
Update to V19.02.11 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC647D
Update to V19.01.14 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC647D
Update to V19.01.14 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC647D
Update to V19.01.14 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC677D
Update to V19.02.11 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC677D
Update to V19.02.11 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC677D
Update to V19.02.11 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC827D
Update to V19.02.11 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC827D
Update to V19.02.11 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC827D
Update to V19.02.11 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC847D
Update to V19.01.14 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC847D
Update to V19.01.14 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC IPC847D
Update to V19.01.14 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC ITP1000
Update to V23.01.04 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC ITP1000
Update to V23.01.04 https://support.industry.siemens.com/cs/us/en/view/109747626
- BehobenSIMATIC ITP1000
Update to V23.01.04 https://support.industry.siemens.com/cs/us/en/view/109747626
Advisories wie diese benennen die exponierten Produkte, die Angreifer auf Ihrer Angriffsfläche ins Visier nehmen. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan