A misconfiguration in the AndroidManifest.xml file in hamza417/inure before build97 allows for task hijacking. This vulnerability permits malicious applications to inherit permissions of the vulnerable app, potentially leading to the exposure of sensitive information. An attacker...
Vendor
hamza417 vulnerabilities
7 published CVES affecting hamza417, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 7
- Critical
- 0
- High
- 2
- Medium
- 4
- Low
- 1
- Unscored
- 0
- CISA KEV
- 0
Products
Latest hamza417 CVEs
Newest publication first
-
MediumCVSS 5.5 EPSS 0.20%
-
LowCVSS 3.3 EPSS 0.27%
Missing Authorization in GitHub repository hamza417/inure prior to Build95.
-
MediumCVSS 5.5 EPSS 0.27%
Missing Authorization in GitHub repository hamza417/inure prior to build94.
-
CVE-2023-4877 Exposure of Sensitive Information to an Unauthorized Actor in hamza417/inure
PublishedHighCVSS 7.5 EPSS 0.44%Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository hamza417/inure prior to build92.
-
CVE-2023-4876 Exposure of Sensitive Information to an Unauthorized Actor in hamza417/inure
PublishedHighCVSS 7.5 EPSS 0.39%Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository hamza417/inure prior to build92.
-
MediumCVSS 5.5 EPSS 0.40%
Improper Input Validation in GitHub repository hamza417/inure prior to build88.
-
MediumCVSS 6.1 EPSS 0.33%
Missing Authorization in GitHub repository hamza417/inure prior to build88.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.