Cloudanix VulnDB

CVE-2024-49195

Critical · 9.8

CVSS

9.8

EPSS

0.6%

Published

Oct 15, 2024

CISA due date

—

Cloudanix analysis

Next patch cycle SSVC: Track

A flaw in a widely used encryption library can let attackers remotely crash or take over systems that handle secure communications or keys.

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

What it actually does

Buffer underrun in pkwrite during opaque key pair serialization causes out-of-bounds memory write in Mbed TLS 3.5.x-3.6.x before 3.6.2.

Why it matters to the business

Remote attackers can crash services or execute arbitrary code in applications performing TLS or cryptographic key operations, leading to service disruption or full system compromise; high ecosystem prevalence via direct mbedtls and downstream Mattermost usage increases exposure urgency despite stable low EPSS.

How an attack unfolds

An unauthenticated attacker sends a network request that triggers pkwrite on an opaque key pair, supplying input that causes the buffer underrun and subsequent memory corruption for potential code execution.

How to fix it

Upgrade armmbed/mbedtls to commit 107ea89daaefb9867ea9121002fbbdf926780e98 (equivalent to 3.6.2) or later; upgrade github.com/mattermost/mattermost-server to 9.2.5+incompatible or later. Apply patches immediately given CVSS 9.8 and memory corruption family.

How to confirm the fix worked

Verify installed version against fixed commit 107ea89daaefb9867ea9121002fbbdf926780e98 or 3.6.2+; recompile and run regression tests for pkwrite opaque key paths; confirm no vulnerable versions remain in dependency trees.

Typical attack path

  1. Identify a target service using vulnerable Mbed TLS for key handling or TLS
  2. Craft and send a malicious request that invokes pkwrite on an opaque key pair
  3. Trigger the buffer underrun to corrupt memory and achieve code execution or denial of service

How to detect it

Review application logs for crashes or errors during key serialization or TLS handshake; inspect process memory dumps for patterns consistent with buffer underruns in pkwrite; correlate with network traffic to services using Mbed TLS.

What your security team should do

  • Patch all instances of Mbed TLS to the fixed commit or 3.6.2 within 48 hours due to remote unauthenticated attack vector
  • Scan dependency graphs for affected armmbed/mbedtls and Mattermost packages and enforce version pinning
  • Monitor for memory corruption indicators in crypto libraries until patches are deployed

The record

Mbed TLS 3.5.x through 3.6.x before 3.6.2 has a buffer underrun in pkwrite when writing an opaque key pair

Affected packages

Ecosystem Package Introduced Fixed
Alpine:v3.20 mbedtls 0 3.6.2-r0
Alpine:v3.21 mbedtls 0 3.6.2-r0
Alpine:v3.22 mbedtls 0 3.6.2-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.2-1
Ubuntu:20.04:LTS mbedtls 0 No fix
Ubuntu:22.04:LTS mbedtls 0 No fix
Ubuntu:24.04:LTS mbedtls 0 No fix
Ubuntu:24.10 mbedtls 0 No fix
Ubuntu:25.04 mbedtls 0 No fix
Ubuntu:Pro:16.04:LTS mbedtls 0 No fix
Ubuntu:Pro:18.04:LTS mbedtls 0 No fix
Ubuntu:Pro:20.04:LTS mbedtls 0 No fix
openSUSE:Leap 16.0 mbedtls 0 3.6.6-bp160.1.1
openSUSE:Tumbleweed mbedtls 0 3.6.2-1.1

Related vulnerabilities