Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 59.50% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2023
CVE-2023-0286High confidence
X.400 address type confusion in X.509 GeneralName
OpenSSL · OpenSSL
Official source article: Siemens SSA-398330 ↗. Check the applicable product and release in the original source.
7.4HighCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 226 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 8 Oct 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs OpenSSL OpenSSL and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 226 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
- Siemens ProductCERT: 5 affected or under-investigation product states without a fixed product state in the same current advisory
- Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
- ABB Product Security Incident Response Team (PSIRT): 2 affected or under-investigation product states without a fixed product state in the same current advisory
- Siemens ProductCERT: 19 affected or under-investigation product states without a fixed product state in the same current advisory
- Siemens ProductCERT: 152 affected or under-investigation product states without a fixed product state in the same current advisory
- Siemens ProductCERT: 2 affected or under-investigation product states without a fixed product state in the same current advisory
- Siemens ProductCERT: 6 affected or under-investigation product states without a fixed product state in the same current advisory
- Siemens ProductCERT: 26 affected or under-investigation product states without a fixed product state in the same current advisory
- Siemens ProductCERT: 3 affected or under-investigation product states without a fixed product state in the same current advisory
- Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
- Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
- Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
- Siemens ProductCERT: 6 affected or under-investigation product states without a fixed product state in the same current advisory
Distribution package intelligence
7 package statesRelease-specific package status
Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · main | openssl | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.0.8-r0 | Alpine Security Database ↗Source updated 8 Oct 2026 |
| Alpine v3.22v3.22 · main | openssl | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.0.8-r0 | Alpine Security Database ↗Source updated 8 Oct 2026 |
| Alpine v3.21v3.21 · main | openssl | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.0.8-r0 | Alpine Security Database ↗Source updated 8 Oct 2026 |
| Debian trixietrixie · source | openssl | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.8-1 | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian bookwormbookworm · source | openssl | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.8-1 | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian forkyforky · source | openssl | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.8-1 | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian sidsid · source | openssl | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.8-1 | Debian Security Tracker ↗Source updated 8 Oct 2026 |
Open-source package ranges3 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| pipcryptography | >= 0.8.1, < 39.0.1 | 39.0.1 | GitHub advisory ↗upstream repository advisory · 4 Nov 2025 |
| rustopenssl-src | < 111.25.0 | 111.25.0 | GitHub advisory ↗upstream repository advisory · 4 Nov 2025 |
| rustopenssl-src | >= 300.0.0, < 300.0.12 | 300.0.12 | GitHub advisory ↗upstream repository advisory · 4 Nov 2025 |
Direct vendor intelligence
15 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2023-0286 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityopenssl: X.400 address type confusion in X.509 GeneralName
The vendor explicitly identifies these products as affected by this CVE.
- AAVMF as a component of Red Hat Enterprise Linux 7
- OVMF as a component of Red Hat Enterprise Linux 7
- ovmf.src as a component of Red Hat Enterprise Linux 7
- openssl.src as a component of Red Hat JBoss Web Server 3
- Summary
- A type confusion vulnerability was found in OpenSSL when OpenSSL X.400 addresses processing inside an X.509 GeneralName. When CRL checking is enabled (for example, the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or cause a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, of which neither needs a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. In this case, this vulnerability is likely only to affect applications that have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the OpenSSL library must be restarted, or the system rebooted.
SSA-028723 · CSAF 2.0 · revision 2 · finalSiemens ProductCERTSSA-028723: Multiple OpenSSL Vulnerabilities in BFCClient Before V2.17
The vendor explicitly identifies these products as affected by this CVE.
- BFCClient
- Summary
- There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- Update to V2.17 or later version. Contact customer support to obtain the update
SSA-398330 · CSAF 2.0 · revision 18 · interimSiemens ProductCERTSSA-398330: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP >= V3.1.0 and < V3.1.5
The vendor explicitly identifies these products as affected by this CVE.
- SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)
- SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)
- SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)
- SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)
- Summary
- There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- Update to V3.1.5 or later version
SSA-455250 · CSAF 2.0 · revision 7 · finalSiemens ProductCERTSSA-455250: Multiple Vulnerabilities in Palo Alto Networks Virtual NGFW on RUGGEDCOM APE1808 Devices Before V11.1.2-h3
The vendor explicitly identifies these products as affected by this CVE.
- RUGGEDCOM APE1808
- Summary
- There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- Upgrade Palo Alto Networks Virtual NGFW V11.1.2-h3. Contact customer support to receive patch and update information
2NGA002579 · CSAF 2.0 · revision 1 · finalABB Product Security Incident Response Team (PSIRT)CVE-2023-0286
The vendor explicitly identifies these products as affected by this CVE.
- ABB M2M Gateway ARM600, firmware versions >=4.1.2|<=5.0.3
- ABB M2M Gateway SW, software versions >=5.0.1|<=5.0.3
- Summary
- X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. When CRL checking is enabled, this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service.
- Remediation
- Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).
SSA-769027 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-769027: Multiple Vulnerabilities fixed in SCALANCE W700 IEEE 802.11ax devices before V3.0.0
The vendor explicitly identifies these products as affected by this CVE.
- SCALANCE WAB762-1 (6GK5762-1AJ00-6AA0)
- SCALANCE WAM763-1 (6GK5763-1AL00-7DA0)
- SCALANCE WAM763-1 (ME) (6GK5763-1AL00-7DC0)
- SCALANCE WAM763-1 (US) (6GK5763-1AL00-7DB0)
- SCALANCE WAM766-1 (6GK5766-1GE00-7DA0)
- SCALANCE WAM766-1 (ME) (6GK5766-1GE00-7DC0)
- SCALANCE WAM766-1 (US) (6GK5766-1GE00-7DB0)
- SCALANCE WAM766-1 EEC (6GK5766-1GE00-7TA0)
- SCALANCE WAM766-1 EEC (ME) (6GK5766-1GE00-7TC0)
- SCALANCE WAM766-1 EEC (US) (6GK5766-1GE00-7TB0)
- SCALANCE WUB762-1 (6GK5762-1AJ00-1AA0)
- SCALANCE WUB762-1 iFeatures (6GK5762-1AJ00-2AA0)
- Summary
- There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- Update to V3.0.0 or later version
SSA-264815 · CSAF 2.0 · revision 4 · interimSiemens ProductCERTSSA-264815: Type Confusion Vulnerability in OpenSSL X.400 Address Processing in SIMATIC Products
The vendor explicitly identifies these products as affected by this CVE.
- SIMATIC Drive Controller CPU 1504D TF (6ES7615-4DF10-0AB0)
- SIMATIC Drive Controller CPU 1507D TF (6ES7615-7DF10-0AB0)
- SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants)
- SIMATIC IPC DiagBase
- SIMATIC IPC DiagMonitor
- SIMATIC S7-1200 CPU family (incl. SIPLUS variants)
- SIMATIC S7-1500 CPU 1510SP F-1 PN (6ES7510-1SJ00-0AB0)
- SIMATIC S7-1500 CPU 1510SP F-1 PN (6ES7510-1SJ01-0AB0)
- SIMATIC S7-1500 CPU 1510SP F-1 PN (6ES7510-1SK03-0AB0)
- SIMATIC S7-1500 CPU 1510SP-1 PN (6ES7510-1DJ00-0AB0)
- SIMATIC S7-1500 CPU 1510SP-1 PN (6ES7510-1DJ01-0AB0)
- SIMATIC S7-1500 CPU 1510SP-1 PN (6ES7510-1DK03-0AB0)
- Summary
- There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- Update to V2.9.7 or later version
SSA-337522 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-337522: Multiple Vulnerabilities in TIM 1531 IRC before V2.4.8
The vendor explicitly identifies these products as affected by this CVE.
- SIPLUS TIM 1531 IRC (6AG1543-1MX00-7XE0)
- TIM 1531 IRC (6GK7543-1MX00-0XE0)
- Summary
- There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- Update to V2.4.8 or later version
SSA-625862 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-625862: Multiple Vulnerabilities in Third-Party Components in SIMATIC CP 1542SP-1 and CP 1543SP-1 before V2.3
The vendor explicitly identifies these products as affected by this CVE.
- SIMATIC CP 1542SP-1 (6GK7542-6UX00-0XE0)
- SIMATIC CP 1542SP-1 IRC (6GK7542-6VX00-0XE0)
- SIMATIC CP 1543SP-1 (6GK7543-6WX00-0XE0)
- SIPLUS ET 200SP CP 1542SP-1 IRC TX RAIL (6AG2542-6VX00-4XE0)
- SIPLUS ET 200SP CP 1543SP-1 ISEC (6AG1543-6WX00-7XE0)
- SIPLUS ET 200SP CP 1543SP-1 ISEC TX RAIL (6AG2543-6WX00-4XE0)
- Summary
- There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- Update to V2.3 or later version
SSA-879734 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-879734: Multiple Vulnerabilities in SCALANCE XM-400/XR-500 before V6.6.1
The vendor explicitly identifies these products as affected by this CVE.
- SCALANCE XM408-4C (6GK5408-4GP00-2AM2)
- SCALANCE XM408-4C (L3 int.) (6GK5408-4GQ00-2AM2)
- SCALANCE XM408-8C (6GK5408-8GS00-2AM2)
- SCALANCE XM408-8C (L3 int.) (6GK5408-8GR00-2AM2)
- SCALANCE XM416-4C (6GK5416-4GS00-2AM2)
- SCALANCE XM416-4C (L3 int.) (6GK5416-4GR00-2AM2)
- SCALANCE XR524-8C, 1x230V (6GK5524-8GS00-3AR2)
- SCALANCE XR524-8C, 1x230V (L3 int.) (6GK5524-8GR00-3AR2)
- SCALANCE XR524-8C, 24V (6GK5524-8GS00-2AR2)
- SCALANCE XR524-8C, 24V (L3 int.) (6GK5524-8GR00-2AR2)
- SCALANCE XR524-8C, 2x230V (6GK5524-8GS00-4AR2)
- SCALANCE XR524-8C, 2x230V (L3 int.) (6GK5524-8GR00-4AR2)
- Summary
- There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- Update to V6.6.1 or later version
SSA-203374 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-203374: Multiple OpenSSL Vulnerabilities in SCALANCE W1750D Devices
The vendor explicitly identifies these products as affected by this CVE.
- SCALANCE W1750D (JP) (6GK5750-2HX01-1AD0)
- SCALANCE W1750D (ROW) (6GK5750-2HX01-1AA0)
- SCALANCE W1750D (USA) (6GK5750-2HX01-1AB0)
- Summary
- There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- Update to V8.10.0.9 or later version The update is available upon request from customer support
SSA-556635 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-556635: Multiple Vulnerabilities in Telecontrol Server Basic before V3.1.2.0
The vendor explicitly identifies these products as affected by this CVE.
- TeleControl Server Basic V3
- Summary
- There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- Update to V3.1.2 or later version
SSA-794697 · CSAF 2.0 · revision 9 · interimSiemens ProductCERTSSA-794697: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP before V1.1
The vendor explicitly identifies these products as affected by this CVE.
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Summary
- There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- Update to V1.1 or later version
SSA-943925 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-943925: Multiple Vulnerabilities in SINEC NMS before V2.0 SP1
The vendor explicitly identifies these products as affected by this CVE.
- SINEC NMS
- Summary
- There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- Update to V2.0 SP1 or later version
SSA-561322 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-561322: Multiple Vulnerabilities in SIMATIC MV500 Devices before V3.3.4
The vendor explicitly identifies these products as affected by this CVE.
- SIMATIC MV540 H (6GF3540-0GE10)
- SIMATIC MV540 S (6GF3540-0CD10)
- SIMATIC MV550 H (6GF3550-0GE10)
- SIMATIC MV550 S (6GF3550-0CD10)
- SIMATIC MV560 U (6GF3560-0LE10)
- SIMATIC MV560 X (6GF3560-0HE10)
- Summary
- There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
- Remediation
- Update to V3.3.4 or later version
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 226 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
What
There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
Why
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
What
There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING. When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
Why
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Access of Resource Using Incompatible Type ('Type Confusion') → disrupt the affected service
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-843 ↗
CWE-843: Access of Resource Using Incompatible Type ('Type Confusion'). The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- Fixed
- openssl-0:1.0.1e-61.el6_10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)
- openssl-0:1.0.1e-61.el6_10.s390 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)
- openssl-0:1.0.1e-61.el6_10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS)
- openssl-0:1.0.1e-61.el6_10.src as a component of Red Hat Enterprise Linux Server (v. 6 ELS)
- openssl-0:1.0.1e-61.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)
- openssl-debuginfo-0:1.0.1e-61.el6_10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)
- openssl-debuginfo-0:1.0.1e-61.el6_10.s390 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)
- openssl-debuginfo-0:1.0.1e-61.el6_10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS)
- openssl-debuginfo-0:1.0.1e-61.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)
- openssl-devel-0:1.0.1e-61.el6_10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)
- openssl-devel-0:1.0.1e-61.el6_10.s390 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)
- openssl-devel-0:1.0.1e-61.el6_10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS)
- openssl-devel-0:1.0.1e-61.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS)
- openssl-debuginfo-0:1.0.1e-61.el6_10.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)
- openssl-debuginfo-0:1.0.1e-61.el6_10.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)
- openssl-debuginfo-0:1.0.1e-61.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)
- openssl-perl-0:1.0.1e-61.el6_10.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)
- openssl-perl-0:1.0.1e-61.el6_10.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)
- openssl-perl-0:1.0.1e-61.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)
- openssl-static-0:1.0.1e-61.el6_10.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)
- openssl-static-0:1.0.1e-61.el6_10.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)
- openssl-static-0:1.0.1e-61.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 6 ELS)
- openssl-1:1.0.2k-26.el7_9.src as a component of Red Hat Enterprise Linux Client (v. 7)
- openssl-1:1.0.2k-26.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)
- openssl-debuginfo-1:1.0.2k-26.el7_9.i686 as a component of Red Hat Enterprise Linux Client (v. 7)
- openssl-debuginfo-1:1.0.2k-26.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)
- openssl-libs-1:1.0.2k-26.el7_9.i686 as a component of Red Hat Enterprise Linux Client (v. 7)
- openssl-libs-1:1.0.2k-26.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)
- openssl-debuginfo-1:1.0.2k-26.el7_9.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
- openssl-debuginfo-1:1.0.2k-26.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
- and 499 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 8 Feb 2023 · Last source change 4 Nov 2025, 19:14 UTC · CWE-843 · Access of Resource Using Incompatible Type ('Type Confusion')
CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2023-0817
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCISA ADP
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Siemens ProductCERT ↗
- Before
- 3.0.0 < 3.0.8; 1.1.1 < 1.1.1t; 1.0.2 < 1.0.2zg · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- 3.0.0 < 3.0.8; 1.1.1 < 1.1.1t; 1.0.2 < 1.0.2zg · Fixed: Update to V3.1.5 or later version
- Vendor guidanceAuthoritative vendor guidance changed: added remediation: search.abb.com/Download.aspx?DocumentID=2NGA002579&LanguageCode=en&DocumentPartId=pdf&Action=Launch; removed remediation: nvd.nist.gov/CVE-2023-0286.ABB Product Security Incident Response Team (PSIRT) ↗
- Before
- remediation: nvd.nist.gov/CVE-2023-0286
- After
- remediation: search.abb.com/Download.aspx?DocumentID=2NGA002579&LanguageCode=en&DocumentPartId=pdf&Action=Launch
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.