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 50.44% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2021
CVE-2021-3712High confidence
Read buffer overruns processing ASN.1 strings
OpenSSL · OpenSSL
Official source article: Siemens SSA-019200 ↗. 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 322 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 5 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 322 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Siemens ProductCERT: 49 affected or under-investigation product states without a fixed product state in the same current advisory
- Siemens ProductCERT: 271 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. | 1.1.1l-r0 | 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. | 1.1.1l-r0 | 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. | 1.1.1l-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Debian trixietrixie · source | openssl | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.1.1l-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. | 1.1.1l-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. | 1.1.1l-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. | 1.1.1l-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
Open-source package ranges1 source-attributed range
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 |
|---|---|---|---|
| rustopenssl-src | < 111.16.0 | 111.16.0 | GitHub advisory ↗github reviewed aggregator · 27 Apr 2026 |
Direct vendor intelligence
6 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-2021-3712 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityopenssl: Read buffer overruns processing ASN.1 strings
The vendor explicitly identifies these products as affected by this CVE.
- rhacm2/management-ingress-rhel8 as a component of Red Hat Advanced Cluster Management for Kubernetes 2
- 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
- openssl098e as a component of Red Hat Enterprise Linux 6
- openssl098e.src as a component of Red Hat Enterprise Linux 6
- openssl098e as a component of Red Hat Enterprise Linux 7
- openssl098e.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
- Summary
- It was found that openssl assumed ASN.1 strings to be NUL terminated. A malicious actor may be able to force an application into calling openssl function with a specially crafted, non-NUL terminated string to deliberately hit this bug, which may result in a crash of the application, causing a Denial of Service attack, or possibly, memory disclosure. The highest threat from this vulnerability is to data confidentiality and system availability.
- 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-019200 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-019200: Multiple Vulnerabilities in SCALANCE W-700 IEEE 802.11n Devices Before V6.6.0
The vendor explicitly identifies these products as affected by this CVE.
- SCALANCE W721-1 RJ45 (6GK5721-1FC00-0AA0)
- SCALANCE W721-1 RJ45 (6GK5721-1FC00-0AB0)
- SCALANCE W722-1 RJ45 (6GK5722-1FC00-0AA0)
- SCALANCE W722-1 RJ45 (6GK5722-1FC00-0AB0)
- SCALANCE W722-1 RJ45 (6GK5722-1FC00-0AC0)
- SCALANCE W734-1 RJ45 (6GK5734-1FX00-0AA0)
- SCALANCE W734-1 RJ45 (6GK5734-1FX00-0AA6)
- SCALANCE W734-1 RJ45 (6GK5734-1FX00-0AB0)
- SCALANCE W734-1 RJ45 (USA) (6GK5734-1FX00-0AB6)
- SCALANCE W738-1 M12 (6GK5738-1GY00-0AA0)
- SCALANCE W738-1 M12 (6GK5738-1GY00-0AB0)
- SCALANCE W748-1 M12 (6GK5748-1GD00-0AA0)
- Summary
- ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).
- Remediation
- Update to V6.6.0 or later version
SSA-244969 · CSAF 2.0 · revision 12 · interimSiemens ProductCERTSSA-244969: OpenSSL Vulnerability in Industrial Products
The vendor explicitly identifies these products as affected by this CVE.
- Industrial Edge - Machine Insight App
- Industrial Edge - PROFINET IO Connector
- RUGGEDCOM RM1224 LTE(4G) EU (6GK6108-4AM00-2BA2)
- RUGGEDCOM RM1224 LTE(4G) NAM (6GK6108-4AM00-2DA2)
- RUGGEDCOM ROX MX5000
- RUGGEDCOM ROX MX5000RE
- RUGGEDCOM ROX RX1400
- RUGGEDCOM ROX RX1500
- RUGGEDCOM ROX RX1501
- RUGGEDCOM ROX RX1510
- RUGGEDCOM ROX RX1511
- RUGGEDCOM ROX RX1512
- Summary
- ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).
- Remediation
- Update to V1.0 SP3 or later version
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
- ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).
- Remediation
- Update to V2.17 or later version. Contact customer support to obtain the update
ARUBA-PSA-2023-002 · CSAF 2.0 · revision 5 · finalHPE Aruba NetworkingAuthenticated Read Buffer Overruns Processing ASN.1 Strings in ArubaOS
The vendor explicitly identifies these products as affected by this CVE.
- SD-Branch 8.7.0.0-2.3.0.x
- AOS-Wi-Fi Controllers and Campus/Remote Access Points
- Summary
- A vulnerability exists which allows an authenticated attacker to access sensitive information via the ArubaOS web-based management interface. Successful exploitation allows an attacker to gain access to some data in a cleartext format exposing other network infrastructure to further compromise.
- Remediation
- PLEASE NOTE - To fully patch all the vulnerabilities disclosed above customers must upgrade to the following versions: - AOS-8.10.x.x: 8.10.0.5 and above - AOS-8.11.x.x: 8.11.0.0 and above - AOS-10.3.x.x: 10.3.1.1 and above - SD-Branch 8.7.0.0-2.3.0.x: 8.7.0.0-2.3.0.9 and above Customers who choose to implement the workarounds listed in the Workaround section below should note that all other vulnerabilities listed in this document are addressed by the following versions: - AOS-8.6.x.x: 8.6.0.20 and above - please note that not all issues are fixed in 8.6.x.x. See the Details section above for specific information - AOS-8.10.x.x: 8.10.0.5 and above - AOS-8.11.x.x: 8.11.0.0 and above - AOS-10.3.x.x: 10.3.1.1 and above - SD-Branch 8.7.0.0-2.3.0.x: 8.7.0.0-2.3.0.9 and above NOTE: At the time of publishing of this Revision-4 of the Security Advisory, following AOS software release trains their End of Maintenance (EoM) milestone: - AOS-8.6.x.x : all - AOS-8.11.x.x : all - AOS-10.3.x.x : all - AOS-10.5.x.x : all - AOS 10.6.x.x : all - SD-Branch 8.7.0.0-2.3.0.x : all Software versions with resolution/fixes for the vulnerabilities covered above can be downloaded from the HPE Networking Support Portal. https://networkingsupport.hpe.com/home/ HPE Aruba Networking does not evaluate or patch AOS branches that have reached their End of Maintenance (EoM) milestone. For Software Release End of Life information, visit: https://networkingsupport.hpe.com/notifications;notificationPageSize=100 ;notificationSortBy=announcementDate;notificationSortDir=desc;notificationCategory=Software%20Release%20End%20of%20Life;
SSA-389290 · CSAF 2.0 · revision 1 · finalSiemens ProductCERTSSA-389290: Third-Party Component Vulnerabilities in SINEC INS
The vendor explicitly identifies these products as affected by this CVE.
- SINEC INS
- Summary
- ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).
- Remediation
- Update to V1.0.1.1 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 322 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
ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).
What
ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).
Why
The product reads data past the end, or before the beginning, of the intended buffer.
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
ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).
Why
The product reads data past the end, or before the beginning, of the intended buffer.
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 → Out-of-bounds Read → 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-125 ↗
CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.
- 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
- rhacm2/management-ingress-rhel8 as a component of Red Hat Advanced Cluster Management for Kubernetes 2
- 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
- openssl098e as a component of Red Hat Enterprise Linux 6
- openssl098e.src as a component of Red Hat Enterprise Linux 6
- openssl098e as a component of Red Hat Enterprise Linux 7
- openssl098e.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.src as a component of Red Hat JBoss Web Server 3
- Fixed
- openssl-1:1.0.2k-23.el7_9.src as a component of Red Hat Enterprise Linux Client (v. 7)
- openssl-1:1.0.2k-23.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)
- openssl-debuginfo-1:1.0.2k-23.el7_9.i686 as a component of Red Hat Enterprise Linux Client (v. 7)
- openssl-debuginfo-1:1.0.2k-23.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)
- openssl-libs-1:1.0.2k-23.el7_9.i686 as a component of Red Hat Enterprise Linux Client (v. 7)
- openssl-libs-1:1.0.2k-23.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)
- openssl-debuginfo-1:1.0.2k-23.el7_9.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
- openssl-debuginfo-1:1.0.2k-23.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
- openssl-devel-1:1.0.2k-23.el7_9.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
- openssl-devel-1:1.0.2k-23.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
- openssl-perl-1:1.0.2k-23.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
- openssl-static-1:1.0.2k-23.el7_9.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
- openssl-static-1:1.0.2k-23.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)
- openssl-debuginfo-1:1.0.2k-23.el7_9.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
- openssl-debuginfo-1:1.0.2k-23.el7_9.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
- openssl-devel-1:1.0.2k-23.el7_9.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
- openssl-devel-1:1.0.2k-23.el7_9.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
- openssl-perl-1:1.0.2k-23.el7_9.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
- openssl-static-1:1.0.2k-23.el7_9.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
- openssl-static-1:1.0.2k-23.el7_9.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)
- openssl-1:1.0.2k-23.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)
- openssl-1:1.0.2k-23.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)
- openssl-1:1.0.2k-23.el7_9.s390x as a component of Red Hat Enterprise Linux Server (v. 7)
- openssl-1:1.0.2k-23.el7_9.src as a component of Red Hat Enterprise Linux Server (v. 7)
- openssl-1:1.0.2k-23.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)
- openssl-debuginfo-1:1.0.2k-23.el7_9.i686 as a component of Red Hat Enterprise Linux Server (v. 7)
- openssl-debuginfo-1:1.0.2k-23.el7_9.ppc as a component of Red Hat Enterprise Linux Server (v. 7)
- openssl-debuginfo-1:1.0.2k-23.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)
- openssl-debuginfo-1:1.0.2k-23.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)
- openssl-debuginfo-1:1.0.2k-23.el7_9.s390 as a component of Red Hat Enterprise Linux Server (v. 7)
- and 261 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 24 Aug 2021 · Last source change 16 Apr 2026, 14:11 UTC · CWE-125 · Out-of-bounds Read
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-2022-4935
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
- Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k); Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y) · 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
- Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k); Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y) · Fixed: Update to V6.6.0 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.