Hamza417 develops Inure, a specialized Android application-analysis and reverse-engineering tool with a modest but focused vulnerability footprint. The recurring exposure centers on authorization and information-disclosure weaknesses alongside input-validation issues, reflecting the sensitive nature of analyzing third-party mobile applications and handling reverse-engineering data. Current severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Hamza417 over time
Signals from CVEs in this vendor scope (6 CVEs).
6 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2023-4877HIGH Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository hamza417/inure prior to build92. | Sep 10, 2023 | 7.5 | 24 | NO | NO |
CVE-2023-4876HIGH Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository hamza417/inure prior to build92. | Sep 10, 2023 | 7.5 | 23 | NO | NO |
CVE-2023-4434MEDIUM Missing Authorization in GitHub repository hamza417/inure prior to build88. | Aug 20, 2023 | 6.1 | 21 | NO | NO |
CVE-2023-4435MEDIUM Improper Input Validation in GitHub repository hamza417/inure prior to build88. | Aug 20, 2023 | 5.5 | 20 | NO | NO |
CVE-2023-5321MEDIUM Missing Authorization in GitHub repository hamza417/inure prior to build94. | Sep 30, 2023 | 5.5 | 18 | NO | NO |
Missing Authorization in GitHub repository hamza417/inure prior to Build95. | Oct 31, 2023 | 3.3 | 14 | NO | NO |
Signals from CVEs in this vendor scope (6 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Hamza417.
Media articles that mention a CVE ID that affects a product developed by Hamza417 — matched by CVE ID, not by vendor name.