| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in hamza417 inure. The affected element is an unknown function. Executing a manipulation can lead to authorization. The identification of this vulnerability is CVE-2023-5321. The attack can only be executed locally. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability classified as critical was found in hamza417 inure. This vulnerability affects an unknown code block. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was shared 09/30/2023. The advisory is available at huntr.dev. This vulnerability was named CVE-2023-5321 since 09/30/2023. The technical details are unknown and an exploit is not available.
Upgrading to version build94 eliminates this vulnerability. Applying the patch 57fda918bfd2fb863f579841a46363fe8e10c29b is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
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.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: 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: 🔍
Upgrade: inure build94
Patch: 57fda918bfd2fb863f579841a46363fe8e10c29b
Timeline
09/30/2023 🔍09/30/2023 🔍
09/30/2023 🔍
10/23/2023 🔍
Sources
Product: github.comAdvisory: 57fda918bfd2fb863f579841a46363fe8e10c29b
Status: Confirmed
CVE: CVE-2023-5321 (🔍)
GCVE (CVE): GCVE-0-2023-5321
GCVE (VulDB): GCVE-100-240994
Entry
Created: 09/30/2023 17:33Updated: 10/23/2023 00:41
Changes: 09/30/2023 17:33 (49), 10/23/2023 00:27 (1), 10/23/2023 00:41 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.