CVE Vulnerabilities

CVE-2023-5862

Missing Authorization

Published: Oct 31, 2023 | Modified: Nov 08, 2023
CVSS 3.x
3.3
LOW
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

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

Weakness

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Affected Software

Name Vendor Start Version End Version
Inure Hamza417 build44 (including) build44 (including)
Inure Hamza417 build45 (including) build45 (including)
Inure Hamza417 build46 (including) build46 (including)
Inure Hamza417 build47 (including) build47 (including)
Inure Hamza417 build48 (including) build48 (including)
Inure Hamza417 build49 (including) build49 (including)
Inure Hamza417 build51 (including) build51 (including)
Inure Hamza417 build52 (including) build52 (including)
Inure Hamza417 build53 (including) build53 (including)
Inure Hamza417 build55 (including) build55 (including)
Inure Hamza417 build56 (including) build56 (including)
Inure Hamza417 build57 (including) build57 (including)
Inure Hamza417 build58 (including) build58 (including)
Inure Hamza417 build59 (including) build59 (including)
Inure Hamza417 build60 (including) build60 (including)
Inure Hamza417 build61 (including) build61 (including)
Inure Hamza417 build62 (including) build62 (including)
Inure Hamza417 build63 (including) build63 (including)
Inure Hamza417 build64 (including) build64 (including)
Inure Hamza417 build65 (including) build65 (including)
Inure Hamza417 build66 (including) build66 (including)
Inure Hamza417 build67 (including) build67 (including)
Inure Hamza417 build68 (including) build68 (including)
Inure Hamza417 build69 (including) build69 (including)
Inure Hamza417 build70 (including) build70 (including)
Inure Hamza417 build71 (including) build71 (including)
Inure Hamza417 build72 (including) build72 (including)
Inure Hamza417 build73 (including) build73 (including)
Inure Hamza417 build74 (including) build74 (including)
Inure Hamza417 build75 (including) build75 (including)
Inure Hamza417 build76 (including) build76 (including)
Inure Hamza417 build77 (including) build77 (including)
Inure Hamza417 build78 (including) build78 (including)
Inure Hamza417 build79 (including) build79 (including)
Inure Hamza417 build80 (including) build80 (including)
Inure Hamza417 build83 (including) build83 (including)
Inure Hamza417 build85 (including) build85 (including)
Inure Hamza417 build86 (including) build86 (including)
Inure Hamza417 build87 (including) build87 (including)
Inure Hamza417 build88 (including) build88 (including)
Inure Hamza417 build89 (including) build89 (including)
Inure Hamza417 build92 (including) build92 (including)
Inure Hamza417 build94 (including) build94 (including)

Extended Description

Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are not applied, users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.

Potential Mitigations

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
  • Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
  • For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
  • One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.

References