Gaby

تسمح ثغرة أمنية في نقطة نهاية إدارة المستخدمين `/api/{org id}/users/{email id}` لمستخدم يحمل دور ”Admin“ بإزالة مستخدم ”Root“ من المؤسسة، مما ينتهك التسلسل الهرمي المقصود للامتيازات. يحدث ذلك بسبب عدم كفاية عمليات التحقق من الدور في الوظيفة `remove user from org`، مما يسمح لمستخدم غير ”Root“ بإزالة الحساب الذي يتمتع بامتيازات أعلى. ونتيجة لذلك، يمكن للمهاجم الذي يحمل دور ’Admin‘ إزالة مستخدمي ”Root“ المهمين، مما قد يمنحه سيطرة كاملة فعليّة من خلال إزالة الحسابات ذات الامتيازات الأعلى. تتأثر نقطة النهاية `DELETE /api/{org id}/users/{email id}`.

The issue concerns the execution of arbitrary binaries due to malicious plugin names, recipients, or identities. This can occur when a plugin name containing a path separator is provided to the `age` CLI or certain `age` APIs, such as `age::plugin::Identity::from str` or `age::plugin::Recipient::from str`. The attack requires a directory matching `age-plugin-*` to exist in the working directory on UNIX systems. The binary is executed with a specific flag and receives the recipient or identity string and other data as standard input, following the `age-plugin` protocol. An equivalent issue was fixed in the reference Go implementation of `age`.

The issue is related to the CORS middleware in Fiber, which allows for insecure configurations. Specifically, it permits setting the Access-Control-Allow-Origin header to a wildcard (`*`) while also having the Access-Control-Allow-Credentials set to true, which goes against recommended security best practices. This misconfiguration can lead to unauthorized access to sensitive user data and expose the system to various types of attacks. The impact of this issue is high.

A vulnerability has been identified in the "/api/{org id}/users" endpoint, allowing any authenticated regular user to add new users with elevated privileges, including the 'root' role, to an organization. This issue circumvents the intended security controls for role assignments, residing in the user creation process where the payload does not validate the user roles. A regular user can manipulate the payload to assign root-level privileges, leading to Unauthorized Privilege Escalation and significantly compromising the application's role-based access control system. This poses a risk to data security, impacting all users, particularly those in administrative roles.

Name of the Vulnerable Software and Affected Versions: OpenObserve versions prior to 0.8.0 Description: A critical issue has been identified in the "/api/{org id}/users/{email id}" endpoint, allowing any authenticated user within an organization to remove any other user, including those with "Admin" and "Root" roles, due to a lack of proper access control. This is caused by the `remove user from org` function not checking for appropriate administrative privileges. The impact is severe, compromising user management integrity and potentially leading to unauthorized system access, administrative lockout, or operational disruptions. Recommendations: For OpenObserve versions prior to 0.8.0, upgrade to release version 0.8.0 to address the issue. As a temporary workaround, consider restricting access to the "/api/{org id}/users/{email id}" endpoint or disabling the `remove user from org` function until the upgrade can be applied.

A Cross-Site Request Forgery (CSRF) vulnerability has been identified in the application, which allows an attacker to obtain tokens and forge malicious requests on behalf of a user. This can lead to unauthorized actions being taken on the user's behalf, potentially compromising the security and integrity of the application. The vulnerability is caused by improper validation and enforcement of CSRF tokens within the application, specifically due to the lack of token association with the original requestor.