aimhubio aim up to 3.25.0 excessive data query operations in a large data table
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in aimhubio aim up to 3.25.0. It has been rated as problematic. Affected by this vulnerability is an unknown functionality. The manipulation leads to excessive data query operations in a large data table. This vulnerability is uniquely identified as CVE-2025-0190. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in aimhubio aim up to 3.25.0. This issue affects an unknown function. The manipulation with an unknown input leads to a excessive data query operations in a large data table vulnerability. Using CWE to declare the problem leads to CWE-1049. The product performs a data query with a large number of joins
and sub-queries on a large data table. Impacted is availability. The summary by CVE is:
In version 3.25.0 of aimhubio/aim, a denial of service vulnerability exists. By tracking a large number of `Text` objects and then querying them simultaneously through the web API, the Aim web server becomes unresponsive to other requests for an extended period while processing and returning these objects. This vulnerability can be exploited repeatedly, leading to a complete denial of service.
The advisory is shared at huntr.com. The identification of this vulnerability is CVE-2025-0190 since 01/03/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (@huntr_ai): 🔍
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: Excessive data query operations in a large data tableCWE: CWE-1049 / CWE-400 / CWE-404
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/03/2025 🔍03/20/2025 🔍
03/20/2025 🔍
03/20/2025 🔍
Sources
Advisory: huntr.comStatus: Not defined
CVE: CVE-2025-0190 (🔍)
GCVE (CVE): GCVE-0-2025-0190
GCVE (VulDB): GCVE-100-300377
Entry
Created: 03/20/2025 15:00Changes: 03/20/2025 15:00 (61)
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.