Simatic S7 1500 Cpu 1517H 3 Pn
Approved changes feed: RSS · Atom
cpe:2.3:a:siemens:simatic_s7-1500_cpu_1517h-3_pn:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Siemens (4bd2a91b-02ad-5c3d-b25f-70697e0c9d7f) |
|---|---|
| Product | Simatic S7 1500 Cpu 1517H 3 Pn (117adbc0-8ade-5da7-81d0-03e237758c6f) |
| 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-2023-46156 |
vulnerable | 2026-06-08 06:12:44.089356 |
Details available
HIGH (7.5)
Affected devices improperly handle specially crafted packets sent to port 102/tcp.
This could allow an attacker to create a denial of service condition. A restart is needed to restore
normal operations.
Published: 2023-12-12T11:27:10.086Z
Updated: 2026-02-25T16:34:35.639Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-37482 |
vulnerable | 2026-06-08 06:08:15.457528 |
Details available
MEDIUM (5.3)
The login functionality of the web server in affected devices does not normalize the response times of login attempts. An unauthenticated remote attacker could exploit this side-channel information to distinguish between valid and invalid usernames.
Published: 2025-02-11T10:26:27.720Z
Updated: 2025-04-08T08:19:41.567Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-38773 |
vulnerable | 2026-06-08 05:47:17.199737 |
Details available
MEDIUM (4.6)
Affected devices do not contain an Immutable Root of Trust in Hardware. With this the integrity of the code executed on the device can not be validated during load-time. An attacker with physical access to the device could use this to replace the boot image of the device and execute arbitrary code.
Published: 2023-01-10T11:39:37.547Z
Updated: 2025-04-03T15:37:09.647Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-30694 |
vulnerable | 2026-06-08 05:43:38.811426 |
Details available
MEDIUM (6.5)
The login endpoint /FormLogin in affected web services does not apply proper origin checking.
This could allow authenticated remote attackers to track the activities of other users via a login cross-site request forgery attack.
Published: 2022-11-08T00:00:00.000Z
Updated: 2025-04-21T13:47:33.635Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-0778 |
vulnerable | 2026-06-08 05:39:11.087807 |
Infinite loop in BN_mod_sqrt() reachable when parsing certificates
The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).
Published: 2022-03-15T17:05:20.382Z
Updated: 2026-05-22T13:28:08.544Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-44695 |
vulnerable | 2026-06-08 05:36:46.716301 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-44694 |
vulnerable | 2026-06-08 05:36:46.698068 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-44693 |
vulnerable | 2026-06-08 05:36:46.507819 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-40365 |
vulnerable | 2026-06-08 05:35:17.639911 | 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.