| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Infoblox BloxOne 2.4. It has been rated as critical. This issue affects some unknown processing. The manipulation leads to behavioral workflow. This vulnerability is listed as CVE-2024-46505. There is no available exploit.
Details
A vulnerability, which was classified as critical, has been found in Infoblox BloxOne 2.4. This issue affects an unknown function. The manipulation with an unknown input leads to a behavioral workflow vulnerability. Using CWE to declare the problem leads to CWE-841. The product supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence. The impact remains unknown. The summary by CVE is:
Infoblox BloxOne v2.4 was discovered to contain a business logic flaw due to thick client vulnerabilities.
The advisory is shared at jayaramyalla.medium.com. The identification of this vulnerability is CVE-2024-46505 since 09/11/2024. 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 01/09/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
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: Behavioral workflowCWE: CWE-841 / CWE-840
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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
09/11/2024 🔍01/09/2025 🔍
01/09/2025 🔍
01/09/2025 🔍
Sources
Advisory: jayaramyalla.medium.comStatus: Not defined
CVE: CVE-2024-46505 (🔍)
GCVE (CVE): GCVE-0-2024-46505
GCVE (VulDB): GCVE-100-291053
Entry
Created: 01/09/2025 21:55Changes: 01/09/2025 21:55 (51)
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.