CVE-2022-0905

Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4...

Authorization

Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4...

CVE-2022-0905

CVE-2022-0905 concerns Gitea (go-gitea/gitea) prior to 1.16.4, with a missing/Improper Authorization vulnerability in PAM/auth flow. Affected component is the Gitea login/authorization path where PAM authentication can skip authorization checks, enabling login for expired accounts or accounts wit...

Cross Site Scripting (XSS)

github.com/go-gitea/gitea is vulnerable to cross-site scripting XSS. The vulnerability exists due to the lack of sanitization in the repository settings in the setting.go file allows the attacker to inject and execute arbitrary Javascript via the URL field in the external wiki/issue tracker...

Cross-site Scripting (XSS)

github.com/go-gitea/gitea is vulnerable to cross-site scripting XSS. The vulnerability exists due to the lack of sanitization, on the values of owner and repo, during the go-get URL generation...

Stored Cross-site Scripting (XSS)

github.com/go-gitea/gitea is vulnerable to stored cross-site scripting XSS. It does not escape the description in DescriptionHTML function, allowing the attacker to inject malicious HTML through it...

Open Redirect

github.com/go-gitea/gitea is vulnerable to open redirect attacks. The vulnerability exists due to the lack of checking on the redirected URL, allowing redirection to external sites...

Cross-Site Scripting (XSS)

github.com/go-gitea/gitea is susceptible to cross-site scripting XSS attacks. The search query and wiki page title parameters are not escaped properly, allowing an attacker to inject and execute arbitrary code through it...

Unauthorized Modification Of Data

github.com/go-gitea/gitea is vulnerable to unauthorized deletion of user emails. A malicious user can modify the HTTP post requests to delete another user's email...

Timing Attacks

github.com/go-gitea/gitea is vulnerable to timing attacks. This vulnerability is caused because the passwords are not compared in constant time, allowing malicious users to guess the valid passwords based on the time that a comparison takes...