Cyber Resilience

CVE-2023-52891

Published
09 July 2024
Modified
15 April 2026
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0046 38th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2023-52891 is a medium-severity Improperly Controlled Sequential Memory Allocation (CWE-1325) vulnerability. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-6 (Resource Availability) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A vulnerability has been identified in SIMATIC Energy Manager Basic (All versions < V7.5), SIMATIC Energy Manager PRO (All versions < V7.5), SIMATIC IPC DiagBase (All versions), SIMATIC IPC DiagMonitor (All versions), SIMIT V10 (All versions), SIMIT V11 (All versions…

more

< V11.1). Unified Automation .NET based OPC UA Server SDK before 3.2.2 used in Siemens products are affected by a similar vulnerability as documented in CVE-2023-27321 for the OPC Foundation UA .NET Standard implementation. A successful attack may lead to high load situation and memory exhaustion, and may block the server.

CWE(s)
CWE-1325

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
attack.mitre.org →
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-2511Shared CWE-1325
CVE-2026-6535Shared CWE-1325
CVE-2025-13945Shared CWE-1325
CVE-2026-8199Shared CWE-1325
CVE-2026-24819Shared CWE-1325
CVE-2026-6869Shared CWE-1325
CVE-2026-6867Shared CWE-1325
CVE-2026-34183Shared CWE-1325
CVE-2025-2240Shared CWE-1325
CVE-2026-6533Shared CWE-1325

Affected Assets

—
All
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V2.4.1
  • V13.1.2
  • V13.2.6

Mitigating Controls (NIST 800-53 r5) AI

SC-6 Resource Availability good match

SC-6 directly enforces resource quotas and priority allocations that stop unbounded sequential memory requests from exhausting the system.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require developers to enforce total memory limits during sequential allocations.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect unbounded allocation patterns, but removing the weakness does not fulfill testing obligations.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle includes resource-management requirements that can prevent uncontrolled per-object allocations.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles can mandate bounded resource usage, but eliminating this CWE does not address broader architectural controls.

A.8.28 Secure coding partial match
prevents

Secure coding standards can require explicit limits on memory per object, yet fixing the weakness alone does not satisfy the full control.

A.8.6 Capacity management partial match
mitigates

Capacity management directly limits total memory consumption across objects, mitigating unbounded sequential allocations.

References