CVE-2023-4876: Exposure of Sensitive Information to an Unauthorized Actor in hamza417/inure
Published Sep 10, 2023
·Updated
Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository hamza417/inure prior to build92.
Affected Software
1 affected component
hamza417 Inure Android<build92
Remediation
Event History
Sep 10, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the vulnerability ID for this security issue?
The vulnerability ID for this security issue is CVE-2023-4876.
2
What is the severity of CVE-2023-4876?
CVE-2023-4876 has a severity rating of 7.9 (High).
3
How does CVE-2023-4876 impact the GitHub repository hamza417/inure?
CVE-2023-4876 exposes sensitive information to an unauthorized actor in the GitHub repository hamza417/inure.
4
What version of hamza417/inure is affected by CVE-2023-4876?
CVE-2023-4876 affects hamza417/inure version up to (but excluding) build92.
5
How can I fix the exposure of sensitive information in hamza417/inure due to CVE-2023-4876?
To fix the exposure of sensitive information in hamza417/inure due to CVE-2023-4876, update to a version beyond build92 and ensure sensitive information is properly protected.