Nssys

Certain endpoints that handle party records lack proper authorization. This allows authenticated users with low-privileged accounts to send requests to these endpoints and modify data beyond their permitted role, resulting in unauthorized changes to party records.

Certain endpoints fail to enforce proper permission checks on inventory records. This allows authenticated users to send requests to these endpoints to modify inventory data beyond the permissions granted to their assigned role.

An issue exists in a record-creation endpoint that accepts the record type from the request and inserts the record while permission checks are disabled. This allows any authenticated user, regardless of their operational role, to specify a privileged record type to create privileged accounts and gain full control of the site.

Certain endpoints fail to enforce proper permission checks, allowing authenticated low-privileged users to deactivate master records and modify data beyond their assigned role permissions.

Certain endpoints fail to enforce proper authorization checks during record status changes. This allows authenticated low-privileged users to modify data beyond their permitted role, bypassing role-based access restrictions.

An issue in proxy tunnel error handling may lead to the exposure of proxy credentials within `ERR PROXY TUNNEL` error messages. This occurs when credentials are embedded in the proxy URL, allowing them to be captured by logs, diagnostics, or other error consumers through specific error handling paths.

An authenticated attacker with administrative privileges can achieve account takeover by stealing session files of other users. The issue arises because the software fails to block the `storage folder` variable from being set to the Flask session directory, typically located at '/tmp/pyLoad/flask'. By setting the `storage folder` to this path, an attacker can use the '/files/get/' endpoint to download session files, allowing them to impersonate other users.