CVE-2023-4877: Exposure of Sensitive Information to an Unauthorized Actor in hamza417/inure
First published: Sun Sep 10 2023(Updated: )
Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository hamza417/inure prior to build92.
Credit: security@huntr.dev security@huntr.dev
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Hamza417 Inure | <build92 | |
| <build92 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2023-4877?
The severity of CVE-2023-4877 is high with a severity value of 7.5.
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.
What software is affected by CVE-2023-4877?
The 'hamza417/inure' Android application prior to build92 is affected by CVE-2023-4877.
How do I fix CVE-2023-4877?
To fix CVE-2023-4877, update the 'hamza417/inure' application to a version beyond build92.
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)
- collector/nvd-index
- agent/references
- agent/author
- agent/type
- agent/severity
- agent/weakness
- agent/title
- agent/remedy
- agent/description
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/softwarecombine
- agent/event
- agent/tags
- agent/source
- vendor/hamza417
- canonical/hamza417 inure