HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2024 2511 unbounded memory growth with session handling in
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Medium · CVSS 5.9CVE-2024-2511

Unbounded memory growth with session handling in TLSv1.3CVE-2024-2511

Answer in brief

CVE-2024-2511 records a Medium severity (CVSS 5.9) vulnerability in Unbounded memory growth with session handling in TLSv1.3. The current sources do not mark it as known exploited. The current feed maps OpenSSL/OpenSSL (generic), Siemens/RUGGEDCOM RM1224 LTE(4G) EU (generic), Siemens/RUGGEDCOM RM1224 LTE(4G) NAM (generic), Siemens/RUGGEDCOM RST2428P (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Apr 8, 2024Updated Oct 15, 2026Source checked Oct 15, 2026First seen by HOL Oct 15, 2026Material review Oct 15, 2026
Upstream Advisory

Key facts

Risk
Medium · CVSS 5.9
Exploitation
Not marked as known exploited
Affected software
31 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 5.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps OpenSSL/OpenSSL (generic), Siemens/RUGGEDCOM RM1224 LTE(4G) EU (generic), Siemens/RUGGEDCOM RM1224 LTE(4G) NAM (generic), Siemens/RUGGEDCOM RST2428P (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
OpenSSL/OpenSSLgeneric>=3.2.0 <3.2.2 || >=3.1.0 <3.1.6 || >=3.0.0 <3.0.14 || >=1.1.1 <1.1.1y3.2.2, 3.1.6, 3.0.14, 1.1.1y
Siemens/RUGGEDCOM RM1224 LTE(4G) EUgeneric>=0 <V8.2V8.2
Siemens/RUGGEDCOM RM1224 LTE(4G) NAMgeneric>=0 <V8.2V8.2
Siemens/RUGGEDCOM RST2428Pgeneric>=0 <V3.1V3.1
Siemens/SCALANCE M804PBgeneric>=0 <V8.2V8.2
Siemens/SCALANCE M812-1 ADSL-Routergeneric>=0 <V8.2V8.2
Siemens/SCALANCE M816-1 ADSL-Routergeneric>=0 <V8.2V8.2
Siemens/SCALANCE M826-2 SHDSL-Routergeneric>=0 <V8.2V8.2
Siemens/SCALANCE M874-2generic>=0 <V8.2V8.2
Siemens/SCALANCE M874-3generic>=0 <V8.2V8.2
Siemens/SCALANCE M874-3 3G-Router (CN)generic>=0 <V8.2V8.2
Siemens/SCALANCE M876-3generic>=0 <V8.2V8.2
Siemens/SCALANCE M876-3 (ROK)generic>=0 <V8.2V8.2
Siemens/SCALANCE M876-4generic>=0 <V8.2V8.2
Siemens/SCALANCE M876-4 (EU)generic>=0 <V8.2V8.2
Siemens/SCALANCE M876-4 (NAM)generic>=0 <V8.2V8.2
Siemens/SCALANCE MUM853-1 (A1)generic>=0 <V8.2V8.2
Siemens/SCALANCE MUM853-1 (B1)generic>=0 <V8.2V8.2
Siemens/SCALANCE MUM853-1 (EU)generic>=0 <V8.2V8.2
Siemens/SCALANCE MUM856-1 (A1)generic>=0 <V8.2V8.2
Siemens/SCALANCE MUM856-1 (B1)generic>=0 <V8.2V8.2
Siemens/SCALANCE MUM856-1 (CN)generic>=0 <V8.2V8.2
Siemens/SCALANCE MUM856-1 (EU)generic>=0 <V8.2V8.2
Siemens/SCALANCE MUM856-1 (RoW)generic>=0 <V8.2V8.2
Siemens/SCALANCE S615 EEC LAN-Routergeneric>=0 <V8.2V8.2
Siemens/SCALANCE S615 LAN-Routergeneric>=0 <V8.2V8.2
Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 familygeneric>=0 <V3.1V3.1
Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric>=V3.1.0 <V3.1.5V3.1.5
Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric>=V3.1.0 <V3.1.5V3.1.5
Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric>=0 <V1.1.1V1.1.1
Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric>=V3.1.0 <V3.1.5V3.1.5

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for OpenSSL/OpenSSL, Siemens/RUGGEDCOM RM1224 LTE(4G) EU, Siemens/RUGGEDCOM RM1224 LTE(4G) NAM.
  2. 2Review the reported fix. Update OpenSSL/OpenSSL to 3.2.2; Siemens/RUGGEDCOM RM1224 LTE(4G) EU to V8.2; Siemens/RUGGEDCOM RM1224 LTE(4G) NAM to V8.2; Siemens/RUGGEDCOM RST2428P to V3.1; Siemens/SCALANCE M804PB to V8.2; Siemens/SCALANCE M812-1 ADSL-Router to V8.2; Siemens/SCALANCE M816-1 ADSL-Router to V8.2; Siemens/SCALANCE M826-2 SHDSL-Router to V8.2; Siemens/SCALANCE M874-2 to V8.2; Siemens/SCALANCE M874-3 to V8.2; Siemens/SCALANCE M874-3 3G-Router (CN) to V8.2; Siemens/SCALANCE M876-3 to V8.2; Siemens/SCALANCE M876-3 (ROK) to V8.2; Siemens/SCALANCE M876-4 to V8.2; Siemens/SCALANCE M876-4 (EU) to V8.2; Siemens/SCALANCE M876-4 (NAM) to V8.2; Siemens/SCALANCE MUM853-1 (A1) to V8.2; Siemens/SCALANCE MUM853-1 (B1) to V8.2; Siemens/SCALANCE MUM853-1 (EU) to V8.2; Siemens/SCALANCE MUM856-1 (A1) to V8.2; Siemens/SCALANCE MUM856-1 (B1) to V8.2; Siemens/SCALANCE MUM856-1 (CN) to V8.2; Siemens/SCALANCE MUM856-1 (EU) to V8.2; Siemens/SCALANCE MUM856-1 (RoW) to V8.2; Siemens/SCALANCE S615 EEC LAN-Router to V8.2; Siemens/SCALANCE S615 LAN-Router to V8.2; Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 family to V3.1; Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP to V3.1.5; Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP to V3.1.5; Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem to V1.1.1; Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFP to V3.1.5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Apr 8, 2024

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Oct 15, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Oct 15, 2026

Sources and claim methodology

  • Source referencecert-portal.siemens.com
  • Source referencecert-portal.siemens.com
  • Source referencecert-portal.siemens.com
  • Source referencecert-portal.siemens.com
  • Source referencecert-portal.siemens.com
  • Source referencecert-portal.siemens.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • Source referencegithub.openssl.org
  • Source referencelists.debian.org
  • Source referencelists.debian.org
  • Source referencesecurity.netapp.com
  • Source referenceopenssl.org
  • Source referenceopenwall.com
Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • SODOLA SL902-SWTGW124AS Buffer Overflow DoS via Multipart Boundary ParserSame generic ecosystem
  • Ellucian WebAdvisor 3.2 Unauthenticated XXE InjectionSame generic ecosystem
  • sgl-project SGLang generate Endpoint io_struct.py denial of serviceSame generic ecosystem
  • sgl-project SGLang Session Cleanup session_controller.py Session.create_req denial of serviceSame generic ecosystem
  • ggml-org whisper.cpp Model Loader whisper_model_load out-of-boundsSame generic ecosystem
  • FreeRDP shadow before 3.32.0 Pre-Authentication Input Injection via Confirm Active bypassSame generic ecosystem

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
CWE-1325
Source
CVE List V5
Source checked
Oct 15, 2026
References
15 linked sources
Open source record