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 1.63% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2023
CVE-2023-0466High confidence
Certificate policy check not enabled
OpenSSL · OpenSSL
Official source article: Siemens SSA-398330 ↗. Check the applicable product and release in the original source.
5.3MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 61 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 severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
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 61 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Siemens ProductCERT: 5 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: 2 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: 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: 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
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. | 0 | Alpine Security Database ↗Source updated 3 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. | 0 | Alpine Security Database ↗Source updated 3 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. | 0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Debian trixietrixie · source | openssl | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.9-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | openssl | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.9-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | openssl | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.9-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | openssl | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.9-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
9 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-0466 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityopenssl: Certificate policy check not enabled
The vendor explicitly identifies these products as affected by this CVE.
- openssl as a component of Red Hat Enterprise Linux 6
- openssl-devel as a component of Red Hat Enterprise Linux 6
- openssl-perl as a component of Red Hat Enterprise Linux 6
- openssl-static as a component of Red Hat Enterprise Linux 6
- openssl.src as a component of Red Hat Enterprise Linux 6
- AAVMF as a component of Red Hat Enterprise Linux 7
- OVMF as a component of Red Hat Enterprise Linux 7
- openssl as a component of Red Hat Enterprise Linux 7
- openssl-devel as a component of Red Hat Enterprise Linux 7
- openssl-libs as a component of Red Hat Enterprise Linux 7
- openssl-perl as a component of Red Hat Enterprise Linux 7
- openssl-static as a component of Red Hat Enterprise Linux 7
- Summary
- A flaw was found in OpenSSL. The X509_VERIFY_PARAM_add0_policy() function is documented to enable the certificate policy check when doing certificate verification implicitly. However, implementing the function does not enable the check, allowing certificates with invalid or incorrect policies to pass the certificate verification. Suddenly enabling the policy check could break existing deployments, so it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. The applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
- Remediation
- Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
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
- The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
- Remediation
- Update to V3.1.5 or later version
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
- The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
- Remediation
- Update to V3.0.0 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
- The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
- Remediation
- Update to V2.4.8 or later version
SSA-341067 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-341067: Multiple vulnerabilities in third-party components in ST7 ScadaConnect before V1.1
The vendor explicitly identifies these products as affected by this CVE.
- ST7 ScadaConnect (6NH7997-5DA10-0AA0)
- Summary
- The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
- Remediation
- Update to V1.1 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
- The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
- 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
- The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
- Remediation
- Update to V6.6.1 or later version
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
- The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
- 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
- The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
- Remediation
- Update to V1.1 or later version
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 61 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
The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
What
The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
Why
The product does not validate, or incorrectly validates, a certificate.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification. As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function. Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument. Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
Why
The product does not validate, or incorrectly validates, a certificate.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
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 → Improper Certificate Validation → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- 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-295 ↗
CWE-295: Improper Certificate Validation. The product does not validate, or incorrectly validates, a certificate.
- 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:L/PR:N/UI:N/S:U/C:N/I:L/A:NCommon 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.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.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.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.- 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
- openssl as a component of Red Hat Enterprise Linux 6
- openssl-devel as a component of Red Hat Enterprise Linux 6
- openssl-perl as a component of Red Hat Enterprise Linux 6
- openssl-static as a component of Red Hat Enterprise Linux 6
- openssl.src as a component of Red Hat Enterprise Linux 6
- AAVMF as a component of Red Hat Enterprise Linux 7
- OVMF as a component of Red Hat Enterprise Linux 7
- openssl as a component of Red Hat Enterprise Linux 7
- openssl-devel as a component of Red Hat Enterprise Linux 7
- openssl-libs as a component of Red Hat Enterprise Linux 7
- openssl-perl as a component of Red Hat Enterprise Linux 7
- openssl-static as a component of Red Hat Enterprise Linux 7
- openssl.src as a component of Red Hat Enterprise Linux 7
- ovmf.src as a component of Red Hat Enterprise Linux 7
- compat-openssl10 as a component of Red Hat Enterprise Linux 8
- compat-openssl10.src as a component of Red Hat Enterprise Linux 8
- openssl as a component of Red Hat Enterprise Linux 8
- openssl-devel as a component of Red Hat Enterprise Linux 8
- openssl-libs as a component of Red Hat Enterprise Linux 8
- openssl-perl as a component of Red Hat Enterprise Linux 8
- openssl-static as a component of Red Hat Enterprise Linux 8
- openssl.src as a component of Red Hat Enterprise Linux 8
- shim-aa64 as a component of Red Hat Enterprise Linux 8
- shim-ia32 as a component of Red Hat Enterprise Linux 8
- shim-x64 as a component of Red Hat Enterprise Linux 8
- shim.src as a component of Red Hat Enterprise Linux 8
- compat-openssl11 as a component of Red Hat Enterprise Linux 9
- compat-openssl11.src as a component of Red Hat Enterprise Linux 9
- shim-aa64 as a component of Red Hat Enterprise Linux 9
- shim-x64 as a component of Red Hat Enterprise Linux 9
- and 2 more
- Fixed
- jbcs-httpd24-openssl-1:1.1.1k-16.el7jbcs.src as a component of Red Hat JBoss Core Services on RHEL 7 Server
- jbcs-httpd24-openssl-1:1.1.1k-16.el7jbcs.x86_64 as a component of Red Hat JBoss Core Services on RHEL 7 Server
- jbcs-httpd24-openssl-debuginfo-1:1.1.1k-16.el7jbcs.x86_64 as a component of Red Hat JBoss Core Services on RHEL 7 Server
- jbcs-httpd24-openssl-devel-1:1.1.1k-16.el7jbcs.x86_64 as a component of Red Hat JBoss Core Services on RHEL 7 Server
- jbcs-httpd24-openssl-libs-1:1.1.1k-16.el7jbcs.x86_64 as a component of Red Hat JBoss Core Services on RHEL 7 Server
- jbcs-httpd24-openssl-perl-1:1.1.1k-16.el7jbcs.x86_64 as a component of Red Hat JBoss Core Services on RHEL 7 Server
- jbcs-httpd24-openssl-static-1:1.1.1k-16.el7jbcs.x86_64 as a component of Red Hat JBoss Core Services on RHEL 7 Server
- jws5-tomcat-native-0:1.2.31-16.redhat_16.el7jws.src as a component of Red Hat JBoss Web Server 5.7 for RHEL 7 Server
- jws5-tomcat-native-0:1.2.31-16.redhat_16.el7jws.x86_64 as a component of Red Hat JBoss Web Server 5.7 for RHEL 7 Server
- jws5-tomcat-native-debuginfo-0:1.2.31-16.redhat_16.el7jws.x86_64 as a component of Red Hat JBoss Web Server 5.7 for RHEL 7 Server
- jbcs-httpd24-openssl-1:1.1.1k-16.el8jbcs.src as a component of Red Hat JBoss Core Services on RHEL 8
- jbcs-httpd24-openssl-1:1.1.1k-16.el8jbcs.x86_64 as a component of Red Hat JBoss Core Services on RHEL 8
- jbcs-httpd24-openssl-debuginfo-1:1.1.1k-16.el8jbcs.x86_64 as a component of Red Hat JBoss Core Services on RHEL 8
- jbcs-httpd24-openssl-devel-1:1.1.1k-16.el8jbcs.x86_64 as a component of Red Hat JBoss Core Services on RHEL 8
- jbcs-httpd24-openssl-libs-1:1.1.1k-16.el8jbcs.x86_64 as a component of Red Hat JBoss Core Services on RHEL 8
- jbcs-httpd24-openssl-libs-debuginfo-1:1.1.1k-16.el8jbcs.x86_64 as a component of Red Hat JBoss Core Services on RHEL 8
- jbcs-httpd24-openssl-perl-1:1.1.1k-16.el8jbcs.x86_64 as a component of Red Hat JBoss Core Services on RHEL 8
- jbcs-httpd24-openssl-static-1:1.1.1k-16.el8jbcs.x86_64 as a component of Red Hat JBoss Core Services on RHEL 8
- jws5-tomcat-native-0:1.2.31-16.redhat_16.el8jws.src as a component of Red Hat JBoss Web Server 5.7 for RHEL 8
- jws5-tomcat-native-0:1.2.31-16.redhat_16.el8jws.x86_64 as a component of Red Hat JBoss Web Server 5.7 for RHEL 8
- jws5-tomcat-native-debuginfo-0:1.2.31-16.redhat_16.el8jws.x86_64 as a component of Red Hat JBoss Web Server 5.7 for RHEL 8
- jws5-tomcat-native-0:1.2.31-16.redhat_16.el9jws.src as a component of Red Hat JBoss Web Server 5.7 for RHEL 9
- jws5-tomcat-native-0:1.2.31-16.redhat_16.el9jws.x86_64 as a component of Red Hat JBoss Web Server 5.7 for RHEL 9
- jws5-tomcat-native-debuginfo-0:1.2.31-16.redhat_16.el9jws.x86_64 as a component of Red Hat JBoss Web Server 5.7 for RHEL 9
- openssl-debuginfo-1:3.0.7-16.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- openssl-debuginfo-1:3.0.7-16.el9_2.i686 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- openssl-debuginfo-1:3.0.7-16.el9_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
- openssl-debuginfo-1:3.0.7-16.el9_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
- openssl-debuginfo-1:3.0.7-16.el9_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- openssl-debugsource-1:3.0.7-16.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
- and 44 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 28 Mar 2023 · Last source change 19 Feb 2025, 17:12 UTC · CWE-295 · Improper Certificate Validation
CVE recordCVE.org · 5.1
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-12520
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
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.1.0 < 3.1.1; 3.0.0 < 3.0.9; 1.1.1 < 1.1.1u; 1.0.2 < 1.0.2zh · 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.1.0 < 3.1.1; 3.0.0 < 3.0.9; 1.1.1 < 1.1.1u; 1.0.2 < 1.0.2zh · Fixed: Update to V3.1.5 or later version
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.