Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Authorization failure in multiple routes of the application. #259

Open
m3n0sd0n4ld opened this issue May 1, 2023 · 1 comment
Open

Authorization failure in multiple routes of the application. #259

m3n0sd0n4ld opened this issue May 1, 2023 · 1 comment

Comments

@m3n0sd0n4ld
Copy link

Describe the bug
A malicious and unauthenticated user would be able to extract confidential and internal information from the application with Helpdesk Community 1.1.10.

  • user names, email addresses, roles, etc...
  • Module information, programs...

In addition, it has been proven that a malicious user would be able to register in the application with administrator role, managing to compromise the application.

To Reproduce
Steps to reproduce the behavior:
The remote and unauthenticated attacker only needs to know the endpoint of the application in question in order to extract the information without being properly authenticated.

The following is an example of several different points of the application:

Affected version

4

Registered user information

9

Departaments

6

Programs

5

In addition, it has been proven that the application is deficient in relevant files such as user registration or update, this would allow the remote attacker to register with malicious accounts and with high privileges (eg. administrator), or even perform escalation of privileges of accounts with lower roles.

Malicious account registration without authentication

7

Access with the malicious account and it is evident that he has administrator privileges of the application.

8

Expected behavior
The application should return a prohibition error due to lack of access, this message must be generic to avoid information leakage that could lead to an enumeration of users or other information.

@m3n0sd0n4ld
Copy link
Author

Hi,

From INCIBE, they indicate me the following identifier CVE-2023-3037 reserved for this vulnerability, this will be effective as of 07/20/2023.

Best regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant