| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in oidcc. It has been classified as problematic. Affected is an unknown function of the component Atom Handler. The manipulation leads to resource consumption. This vulnerability is listed as CVE-2024-31209. The attack must be carried out locally. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability was found in oidcc (unknown version) and classified as problematic. This issue affects an unknown code block of the component Atom Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-31209 since 03/29/2024. The exploitation is known to be difficult. An attack has to be approached locally. Additional levels of successful authentication are necessary for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.6
VulDB Base Score: 4.1
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (GitHub, Inc.): 🔍
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: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
03/29/2024 🔍04/04/2024 🔍
04/04/2024 🔍
05/09/2024 🔍
Sources
Advisory: 2f304d877c7e0613d6fd952d7feacbf40dbc355cStatus: Confirmed
CVE: CVE-2024-31209 (🔍)
GCVE (CVE): GCVE-0-2024-31209
GCVE (VulDB): GCVE-100-259313
Entry
Created: 04/04/2024 08:00Updated: 05/09/2024 12:38
Changes: 04/04/2024 08:00 (50), 05/09/2024 12:31 (3), 05/09/2024 12:38 (12)
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.