CVE-2023-4876: 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 vulnerability ID for this security issue?
The vulnerability ID for this security issue is CVE-2023-4876.
What is the severity of CVE-2023-4876?
CVE-2023-4876 has a severity rating of 7.9 (High).
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.
What version of hamza417/inure is affected by CVE-2023-4876?
CVE-2023-4876 affects hamza417/inure version up to (but excluding) build92.
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.
- collector/nvd-index
- agent/references
- agent/author
- agent/type
- agent/severity
- agent/remedy
- agent/weakness
- agent/title
- 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/tags
- agent/event
- agent/source
- vendor/hamza417
- canonical/hamza417 inure