Cloudanix VulnDB

CVE-2025-27810

Medium · 5.4

CVSS

5.4

EPSS

0.3%

Published

Mar 25, 2025

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A bug in a common encryption library can let attackers reuse old login data to slip into systems without proper credentials when certain rare errors occur.

Exploitation
Remote Unauthenticated
Attacker needs
None
Complexity
High
Impact
Privilege Gain
Component
Library
Class
Memory Corruption
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Under failed memory allocation or hardware errors, Mbed TLS reuses uninitialized stack memory when constructing the TLS Finished handshake message, allowing an attacker to influence or replay authentication material.

Why it matters to the business

Organizations using affected TLS libraries face elevated risk of authentication bypass in encrypted sessions; the issue affects widely embedded cryptographic components and downstream packages, requiring prioritized upgrades despite low observed exploitation rates.

How an attack unfolds

An attacker triggers memory allocation failures or hardware faults during a TLS handshake, causing the library to emit a Finished message containing residual stack data; the attacker then captures and replays this message to bypass authentication checks in subsequent sessions.

How to fix it

Upgrade Mbed TLS to 2.28.10 or 3.6.3 (commit 2fc8413bfcb51354c8e679141b17b3f1a5942561) or later; upgrade PaddlePaddle to 2.6.0 or later. Verify the update resolves the uninitialized memory path in Finished message construction.

How to confirm the fix worked

Confirm the installed library version meets or exceeds the fixed releases; run regression tests that simulate allocation failures during handshakes and verify the Finished message contains only properly initialized data.

Typical attack path

  1. Identify a target service using vulnerable Mbed TLS during TLS negotiation
  2. Force memory pressure or hardware faults on the target to induce allocation failures
  3. Capture the resulting TLS Finished message containing uninitialized data
  4. Replay the captured message to authenticate without valid credentials

How to detect it

Review TLS handshake logs for Finished messages sent immediately after allocation-related errors; correlate with replayed session identifiers or unexpected successful authentications following handshake failures.

What your security team should do

  • Immediately inventory all uses of Mbed TLS and PaddlePaddle and schedule upgrades to the listed fixed versions
  • Prioritize patching in any externally facing TLS endpoints given the authentication-bypass potential
  • Add memory-allocation-failure simulation to CI test suites for cryptographic libraries

The record

Mbed TLS before 2.28.10 and 3.x before 3.6.3, in some cases of failed memory allocation or hardware errors, uses uninitialized stack memory to compose the TLS Finished message, potentially leading to authentication bypasses such as replays.

Affected packages

Ecosystem Package Introduced Fixed
Alpine:v3.18 mbedtls 0 2.28.10-r0
Alpine:v3.19 mbedtls 0 2.28.10-r0
Alpine:v3.20 mbedtls 0 3.6.3-r0
Alpine:v3.21 mbedtls 0 3.6.3-r0
Alpine:v3.22 mbedtls 0 3.6.3-r0
Debian:11 mbedtls 0 No fix
Debian:12 mbedtls 0 No fix
Debian:13 mbedtls 0 No fix
Debian:14 mbedtls 0 3.6.3-1
Julia MbedTLS_jll 0 2.28.10+0
openSUSE:Leap 16.0 mbedtls 0 3.6.6-bp160.1.1
openSUSE:Leap 16.0 mbedtls-2 0 2.28.10-bp160.1.1
openSUSE:Tumbleweed mbedtls-2 0 2.28.10-1.1

Related vulnerabilities