CVE-2023-5321 | Missing Authorization in hamza417/inure

Exp

Missing Authorization in GitHub repository hamza417/inure prior to build94.

Published: 2023-09-30 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-5321 is rated Exploit Available (50/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.03%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2023-5321

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2023-5321

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.05% 0.03% -0.02%
2 2025-11-18 0.03% 0.05% +0.02%
3 2025-04-15 — 0.03% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-5321

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 3.6 [email protected]
5.1 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.5 2.5 [email protected]

Weakness enumeration for CVE-2023-5321

Affected software / configurations for CVE-2023-5321

Vendor Product Version Raw CPE
hamza417 inure build44 cpe:2.3:a:hamza417:inure:build44:*:*:*:*:android:*:*
hamza417 inure build45 cpe:2.3:a:hamza417:inure:build45:*:*:*:*:android:*:*
hamza417 inure build46 cpe:2.3:a:hamza417:inure:build46:*:*:*:*:android:*:*
hamza417 inure build47 cpe:2.3:a:hamza417:inure:build47:*:*:*:*:android:*:*
hamza417 inure build48 cpe:2.3:a:hamza417:inure:build48:*:*:*:*:android:*:*
hamza417 inure build49 cpe:2.3:a:hamza417:inure:build49:*:*:*:*:android:*:*
hamza417 inure build51 cpe:2.3:a:hamza417:inure:build51:*:*:*:*:android:*:*
hamza417 inure build52 cpe:2.3:a:hamza417:inure:build52:*:*:*:*:android:*:*
hamza417 inure build53 cpe:2.3:a:hamza417:inure:build53:*:*:*:*:android:*:*
hamza417 inure build55 cpe:2.3:a:hamza417:inure:build55:*:*:*:*:android:*:*
hamza417 inure build56 cpe:2.3:a:hamza417:inure:build56:*:*:*:*:android:*:*
hamza417 inure build57 cpe:2.3:a:hamza417:inure:build57:*:*:*:*:android:*:*
hamza417 inure build58 cpe:2.3:a:hamza417:inure:build58:*:*:*:*:android:*:*
hamza417 inure build59 cpe:2.3:a:hamza417:inure:build59:*:*:*:*:android:*:*
hamza417 inure build60 cpe:2.3:a:hamza417:inure:build60:*:*:*:*:android:*:*
hamza417 inure build61 cpe:2.3:a:hamza417:inure:build61:*:*:*:*:android:*:*
hamza417 inure build62 cpe:2.3:a:hamza417:inure:build62:*:*:*:*:android:*:*
hamza417 inure build63 cpe:2.3:a:hamza417:inure:build63:*:*:*:*:android:*:*
hamza417 inure build64 cpe:2.3:a:hamza417:inure:build64:*:*:*:*:android:*:*
hamza417 inure build65 cpe:2.3:a:hamza417:inure:build65:*:*:*:*:android:*:*
hamza417 inure build66 cpe:2.3:a:hamza417:inure:build66:*:*:*:*:android:*:*
hamza417 inure build67 cpe:2.3:a:hamza417:inure:build67:*:*:*:*:android:*:*
hamza417 inure build68 cpe:2.3:a:hamza417:inure:build68:*:*:*:*:android:*:*
hamza417 inure build69 cpe:2.3:a:hamza417:inure:build69:*:*:*:*:android:*:*
hamza417 inure build70 cpe:2.3:a:hamza417:inure:build70:*:*:*:*:android:*:*
hamza417 inure build71 cpe:2.3:a:hamza417:inure:build71:*:*:*:*:android:*:*
hamza417 inure build72 cpe:2.3:a:hamza417:inure:build72:*:*:*:*:android:*:*
hamza417 inure build73 cpe:2.3:a:hamza417:inure:build73:*:*:*:*:android:*:*
hamza417 inure build74 cpe:2.3:a:hamza417:inure:build74:*:*:*:*:android:*:*
hamza417 inure build75 cpe:2.3:a:hamza417:inure:build75:*:*:*:*:android:*:*
hamza417 inure build76 cpe:2.3:a:hamza417:inure:build76:*:*:*:*:android:*:*
hamza417 inure build77 cpe:2.3:a:hamza417:inure:build77:*:*:*:*:android:*:*
hamza417 inure build78 cpe:2.3:a:hamza417:inure:build78:*:*:*:*:android:*:*
hamza417 inure build79 cpe:2.3:a:hamza417:inure:build79:*:*:*:*:android:*:*
hamza417 inure build80 cpe:2.3:a:hamza417:inure:build80:*:*:*:*:android:*:*
hamza417 inure build83 cpe:2.3:a:hamza417:inure:build83:*:*:*:*:android:*:*
hamza417 inure build85 cpe:2.3:a:hamza417:inure:build85:*:*:*:*:android:*:*
hamza417 inure build86 cpe:2.3:a:hamza417:inure:build86:*:*:*:*:android:*:*
hamza417 inure build87 cpe:2.3:a:hamza417:inure:build87:*:*:*:*:android:*:*
hamza417 inure build88 cpe:2.3:a:hamza417:inure:build88:*:*:*:*:android:*:*
hamza417 inure build89 cpe:2.3:a:hamza417:inure:build89:*:*:*:*:android:*:*
hamza417 inure build92 cpe:2.3:a:hamza417:inure:build92:*:*:*:*:android:*:*
hamza417 inure build93 cpe:2.3:a:hamza417:inure:build93:*:*:*:*:android:*:*

References for CVE-2023-5321

cvelogic Threat Intelligence