AdaCore Ada Web Server 25.0.0 TLS Configuration channel accessible
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in AdaCore Ada Web Server 25.0.0. Impacted is an unknown function of the component TLS Configuration Handler. This manipulation causes channel accessible. The identification of this vulnerability is CVE-2024-55581. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in AdaCore Ada Web Server 25.0.0. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component TLS Configuration Handler. The manipulation with an unknown input leads to a channel accessible vulnerability. The CWE definition for the vulnerability is CWE-300. The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint. As an impact it is known to affect integrity. The summary by CVE is:
When AdaCore Ada Web Server 25.0.0 is linked with GnuTLS, the default behaviour of AWS.Client is vulnerable to a man-in-the-middle attack because of lack of verification of an HTTPS server's certificate (unless the using program specifies a TLS configuration).
The advisory is shared at docs.adacore.com. This vulnerability is known as CVE-2024-55581 since 12/09/2024. 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 price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/01/2025). MITRE ATT&CK project uses the attack technique T1557 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 232554 (Debian dla-4080 : libaws-bin - security update), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Tenable (232554) and EUVD (EUVD-2025-5281). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Channel accessibleCWE: CWE-300
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: 232554
Nessus Name: Debian dla-4080 : libaws-bin - security update
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/09/2024 🔍02/27/2025 🔍
02/27/2025 🔍
06/01/2025 🔍
Sources
Advisory: docs.adacore.comStatus: Confirmed
CVE: CVE-2024-55581 (🔍)
GCVE (CVE): GCVE-0-2024-55581
GCVE (VulDB): GCVE-100-297709
EUVD: 🔍
Entry
Created: 02/27/2025 07:58Updated: 06/01/2025 09:39
Changes: 02/27/2025 07:58 (53), 03/11/2025 09:37 (2), 04/08/2025 05:17 (1), 06/01/2025 09:39 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.