CVE-2023-4877: 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 severity of CVE-2023-4877?
The severity of CVE-2023-4877 is high with a severity value of 7.5.
2
How does CVE-2023-4877 affect the 'hamza417/inure' GitHub repository?
CVE-2023-4877 exposes sensitive information to an unauthorized actor in the 'hamza417/inure' GitHub repository prior to build92.
3
What software is affected by CVE-2023-4877?
The 'hamza417/inure' Android application prior to build92 is affected by CVE-2023-4877.
4
How do I fix CVE-2023-4877?
To fix CVE-2023-4877, update the 'hamza417/inure' application to a version beyond build92.
5
Where can I find more information about CVE-2023-4877?
More information about CVE-2023-4877 can be found in the following references: - [GitHub commit](https://github.com/hamza417/inure/commit/09762e8c059be5983ca55e6424b2b5992fa740e7) - [Huntr bounty](https://huntr.dev/bounties/168e9299-f8ff-40d6-9def-d097b38bad84)