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 52.42% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2024
CVE-2024-2511High confidence
Unbounded memory growth with session handling in TLSv1.3
OpenSSL · OpenSSL
Official source articles: Siemens SSA-265688 ↗ · Siemens SSA-398330 ↗. Check the applicable product and release in the original source.
5.9MediumCVSS 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 54 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:High, 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 54 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: 2 affected or under-investigation product states 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: 19 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
Distribution package intelligence
9 package statesRelease-specific package status
Alpine, Debian, ubuntu 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.2.1-r2 | 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. | 3.2.1-r2 | 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. | 3.2.1-r2 | 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.2.2-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.14-1~deb12u1 | 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.2.2-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.2.2-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | edk2 | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 2024.02-2ubuntu0.6 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | openssl | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 3.0.13-0ubuntu3.2 | Canonical Ubuntu Security ↗Source updated 5 Oct 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.
SSA-265688 · CSAF 2.0 · revision 13 · interimSiemens ProductCERTSSA-265688: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP V1.1
The vendor explicitly identifies these products as affected by this CVE.
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Summary
- Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions. An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation. This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
- Remediation
- Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-613116 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-613116: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.1
The vendor explicitly identifies these products as affected by this CVE.
- RUGGEDCOM RST2428P (6GK6242-6PA00)
- SCALANCE XCM-/XRM-/XCH-/XRH-300 family
- Summary
- Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions. An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation. This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
- Remediation
- Update to V3.1 or later version
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
- Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions. An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation. This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
- 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
- Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions. An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation. This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
- Remediation
- Update to V3.0.0 or later version
SSA-354112 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-354112: Multiple Vulnerabilities in SCALANCE M-800 Family Before V8.2
The vendor explicitly identifies these products as affected by this CVE.
- RUGGEDCOM RM1224 LTE(4G) EU (6GK6108-4AM00-2BA2)
- RUGGEDCOM RM1224 LTE(4G) NAM (6GK6108-4AM00-2DA2)
- SCALANCE M804PB (6GK5804-0AP00-2AA2)
- SCALANCE M812-1 ADSL-Router (6GK5812-1AA00-2AA2)
- SCALANCE M812-1 ADSL-Router (6GK5812-1BA00-2AA2)
- SCALANCE M816-1 ADSL-Router (6GK5816-1AA00-2AA2)
- SCALANCE M816-1 ADSL-Router (6GK5816-1BA00-2AA2)
- SCALANCE M826-2 SHDSL-Router (6GK5826-2AB00-2AB2)
- SCALANCE M874-2 (6GK5874-2AA00-2AA2)
- SCALANCE M874-3 (6GK5874-3AA00-2AA2)
- SCALANCE M874-3 3G-Router (CN) (6GK5874-3AA00-2FA2)
- SCALANCE M876-3 (6GK5876-3AA02-2BA2)
- Summary
- Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation. This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
- Remediation
- Update to V8.2 or later version
SSA-915275 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-915275: Multiple Vulnerabilities in SINEC INS Before V1.0 SP2 Update 3
The vendor explicitly identifies these products as affected by this CVE.
- SINEC INS
- Summary
- Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation. This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
- Remediation
- Update to V1.0 SP2 Update 3 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 54 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
Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation. This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
What
Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation. This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
Why
The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.
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
Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation. This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
Why
The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.
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 → Improperly Controlled Sequential Memory Allocation → 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-1325 ↗
CWE-1325: Improperly Controlled Sequential Memory Allocation. The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.
- 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:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.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
- 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
- Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04
Evidence and provenance
Published 8 Apr 2024 · Last source change 12 May 2026, 11:30 UTC · CWE-1325 · Improperly Controlled Sequential Memory Allocation
CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
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-2024-27460
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCNA
NVD statusNVD not scheduled
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.2.0 < 3.2.2; 3.1.0 < 3.1.6; 3.0.0 < 3.0.14; 1.1.1 < 1.1.1y · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- 3.2.0 < 3.2.2; 3.1.0 < 3.1.6; 3.0.0 < 3.0.14; 1.1.1 < 1.1.1y · Fixed: Update to V3.1.5 or later version
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Siemens ProductCERT ↗
- Before
- Awaiting fix
- After
- Patch available
CVE published
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.