CVE-2023-5321: Missing Authorization in hamza417/inure

Published Sep 30, 2023
·
Updated

Missing Authorization in GitHub repository hamza417/inure prior to build94.

Affected Software

43 affected components
hamza417 Inure Android=build44
hamza417 Inure Android=build45
hamza417 Inure Android=build46
hamza417 Inure Android=build47
hamza417 Inure Android=build48
hamza417 Inure Android=build49
hamza417 Inure Android=build51
hamza417 Inure Android=build52
hamza417 Inure Android=build53
hamza417 Inure Android=build55
hamza417 Inure Android=build56
hamza417 Inure Android=build57
hamza417 Inure Android=build58
hamza417 Inure Android=build59
hamza417 Inure Android=build60
hamza417 Inure Android=build61
hamza417 Inure Android=build62
hamza417 Inure Android=build63
hamza417 Inure Android=build64
hamza417 Inure Android=build65
hamza417 Inure Android=build66
hamza417 Inure Android=build67
hamza417 Inure Android=build68
hamza417 Inure Android=build69
hamza417 Inure Android=build70
hamza417 Inure Android=build71
hamza417 Inure Android=build72
hamza417 Inure Android=build73
hamza417 Inure Android=build74
hamza417 Inure Android=build75
hamza417 Inure Android=build76
hamza417 Inure Android=build77
hamza417 Inure Android=build78
hamza417 Inure Android=build79
hamza417 Inure Android=build80
hamza417 Inure Android=build83
hamza417 Inure Android=build85
hamza417 Inure Android=build86
hamza417 Inure Android=build87
hamza417 Inure Android=build88
hamza417 Inure Android=build89
hamza417 Inure Android=build92
hamza417 Inure Android=build93

Event History

Sep 30, 2023
CVE Published
via MITRE·01:43 PM
Data Sourced
via MITRE·01:43 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2023-5321?

The severity of CVE-2023-5321 is medium with a CVSS score of 5.1.

2

How does CVE-2023-5321 affect Hamza417 Inure?

CVE-2023-5321 affects Hamza417 Inure prior to build94.

3

How can I fix CVE-2023-5321 in Hamza417 Inure?

To fix CVE-2023-5321 in Hamza417 Inure, update to build94 or later.

4

Where can I find more information about CVE-2023-5321?

You can find more information about CVE-2023-5321 at the following references: [Reference 1](https://github.com/hamza417/inure/commit/57fda918bfd2fb863f579841a46363fe8e10c29b), [Reference 2](https://huntr.dev/bounties/b1becc68-e738-458f-bd99-06ee77580d3a).

5

What is the Common Weakness Enumeration (CWE) for CVE-2023-5321?

The Common Weakness Enumeration (CWE) for CVE-2023-5321 is CWE-862.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203