Mbed TLS up to 2.28.9/3.6.2 TLS Finished Message uninitialized resource
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Mbed TLS up to 2.28.9/3.6.2. This impacts an unknown function of the component TLS Finished Message Handler. This manipulation causes uninitialized resource. This vulnerability is tracked as CVE-2025-27810. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Mbed TLS up to 2.28.9/3.6.2. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the component TLS Finished Message Handler. The manipulation with an unknown input leads to a uninitialized resource vulnerability. The CWE definition for the vulnerability is CWE-908. The product uses or accesses a resource that has not been initialized. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is known as CVE-2025-27810 since 03/07/2025. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 276298 (TencentOS Server 4: mbedtls (TSSA-2025:0337)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 2.28.10 or 3.6.3 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (276298) and EUVD (EUVD-2025-14831). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.8
NVD Vector: 🔍
CNA Base Score: 5.4
CNA Vector (MITRE): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Uninitialized resourceCWE: CWE-908
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 276298
Nessus Name: TencentOS Server 4: mbedtls (TSSA-2025:0337)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: TLS 2.28.10/3.6.3
Timeline
03/07/2025 🔍03/25/2025 🔍
03/25/2025 🔍
11/24/2025 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2025-27810 (🔍)
GCVE (CVE): GCVE-0-2025-27810
GCVE (VulDB): GCVE-100-301057
EUVD: 🔍
Entry
Created: 03/25/2025 07:13Updated: 11/24/2025 05:22
Changes: 03/25/2025 07:13 (63), 05/27/2025 02:03 (1), 10/30/2025 16:30 (12), 11/24/2025 05:22 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.