Cyber Resilience

CVE-2024-27099

Memory Safety in Microsoft Azure Uamqp ≤ 2023-2-08

Memory Safety
Published
27 February 2024
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.014 70th percentile
Risk Priority 74 floored blend · peak EPSS

Summary

CVE-2024-27099 is a critical-severity Double Free (CWE-415) vulnerability in Microsoft Azure Uamqp. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked in the top 30% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

The uAMQP is a C library for AMQP 1.0 communication to Azure Cloud Services. When processing an incorrect `AMQP_VALUE` failed state, may cause a double free problem. This may cause a RCE. Update submodule with commit 2ca42b6e4e098af2d17e487814a91d05f6ae4987.

CWE(s)
CWE-415

Related Threats

MITRE ATT&CK Enterprise Techniques

T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
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 →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-25110Same product: Microsoft Azure Uamqp
CVE-2024-21646Same product: Microsoft Azure Uamqp
CVE-2024-43514Same vendor: Microsoft
CVE-2023-36420Same vendor: Microsoft
CVE-2023-29366Same vendor: Microsoft
CVE-2024-38157Same vendor: Microsoft
CVE-2025-47975Same vendor: Microsoft
CVE-2023-35371Same vendor: Microsoft
CVE-2024-49014Same vendor: Microsoft
CVE-2026-33838Same vendor: Microsoft

Affected Assets

microsoft
azure uamqp
≤ 2023-2-08

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation explicitly includes dynamic analysis and fuzzing that locate double-free defects before release.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles can require memory-safe allocation patterns or language features that structurally eliminate double-free opportunities.

SI-2 Flaw Remediation partial match

Flaw remediation processes require identification and correction of memory-management defects such as double free once discovered.

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 full match
prevents

Secure SDLC practices directly prevent double-free errors via static analysis, safe memory APIs, and testing.

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 in development can detect double-free conditions before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle includes memory-safety practices that can prevent double-free bugs.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate memory-safety rules that reduce double-free risk.

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

Secure system architecture and engineering principles can prescribe safe memory-management patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address proper use of free() and similar functions.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248590 OL 8 must clear the page allocator to prevent use-after-free attacks. prevents CWE-415

References