| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in hamza417 inure and classified as problematic. Affected is an unknown function. Performing a manipulation results in authorization. This vulnerability is known as CVE-2023-4434. No exploit is available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as problematic has been found in hamza417 inure (the affected version unknown). This affects an unknown part. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 08/20/2023. It is possible to read the advisory at huntr.dev. This vulnerability is uniquely identified as CVE-2023-4434 since 08/20/2023. The technical details are unknown and an exploit is not publicly available.
Applying the patch 2176af74ca3a81fd001e6cc8eea5a8306f484fbb is able to eliminate this problem. The bugfix is ready for download at github.com.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
License
Website
- Product: https://github.com/hamza417/inure/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
CNA Base Score: 5.1
CNA Vector (huntr.dev): 🔍
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: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 2176af74ca3a81fd001e6cc8eea5a8306f484fbb
Timeline
08/20/2023 🔍08/20/2023 🔍
08/20/2023 🔍
09/13/2023 🔍
Sources
Product: github.comAdvisory: 2176af74ca3a81fd001e6cc8eea5a8306f484fbb
Status: Confirmed
CVE: CVE-2023-4434 (🔍)
GCVE (CVE): GCVE-0-2023-4434
GCVE (VulDB): GCVE-100-237555
Entry
Created: 08/20/2023 08:49Updated: 09/13/2023 18:05
Changes: 08/20/2023 08:49 (37), 09/13/2023 17:57 (1), 09/13/2023 18:05 (21)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.