Gitea 1.2.0 for Jenkins

CPE Details

Gitea 1.2.0 for Jenkins
gitea
gitea
1.2.0
2022-12-12
16h58 +00:00
2022-12-14
19h30 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:gitea:gitea:1.2.0:*:*:*:*:jenkins:*:*

Informations

Vendor

gitea

Product

gitea

Version

1.2.0

Target Software

jenkins

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2022-38795 2023-08-06 22h00 +00:00 In Gitea through 1.17.1, repo cloning can occur in the migration function.
6.5
Medium
CVE-2023-3515 2023-07-05 14h12 +00:00 Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4.
4.4
Medium
CVE-2022-46685 2022-12-06 23h00 +00:00 In Jenkins Gitea Plugin 1.4.4 and earlier, the implementation of Gitea personal access tokens did not support credentials masking, potentially exposing them through the build log.
4.3
Medium
CVE-2022-42968 2022-10-15 22h00 +00:00 Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.
9.8
Critical
CVE-2022-38183 2022-08-11 22h00 +00:00 In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to private issue titles.
6.5
Medium
CVE-2022-1928 2022-05-28 22h00 +00:00 Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9.
5.4
Medium
CVE-2022-30781 2022-05-15 22h00 +00:00 Gitea before 1.16.7 does not escape git fetch remote.
7.5
High
CVE-2022-1058 2022-03-24 13h15 +00:00 Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5.
6.1
Medium
CVE-2021-29134 2022-03-15 19h30 +00:00 The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL.
5.3
Medium
CVE-2022-0905 2022-03-09 23h00 +00:00 Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4.
7.1
High
CVE-2021-45331 2022-02-09 16h22 +00:00 An Authentication Bypass vulnerability exists in Gitea before 1.5.0, which could let a malicious user gain privileges. If captured, the TOTP code for the 2FA can be submitted correctly more than once.
9.8
Critical
CVE-2021-45330 2022-02-09 16h16 +00:00 An issue exsits in Gitea through 1.15.7, which could let a malicious user gain privileges due to client side cookies not being deleted and the session remains valid on the server side for reuse.
9.8
Critical
CVE-2021-45329 2022-02-08 21h26 +00:00 Cross Site Scripting (XSS) vulnerability exists in Gitea before 1.5.1 via the repository settings inside the external wiki/issue tracker URL field.
6.1
Medium
CVE-2021-45328 2022-02-08 14h14 +00:00 Gitea before 1.4.3 is affected by URL Redirection to Untrusted Site ('Open Redirect') via internal URLs.
6.1
Medium
CVE-2021-45327 2022-02-08 13h57 +00:00 Gitea before 1.11.2 is affected by Trusting HTTP Permission Methods on the Server Side when referencing the vulnerable admin or user API. which could let a remote malisious user execute arbitrary code.
9.8
Critical
CVE-2021-45326 2022-02-08 13h48 +00:00 Cross Site Request Forgery (CSRF) vulnerability exists in Gitea before 1.5.2 via API routes.This can be dangerous especially with state altering POST requests.
8.8
High
CVE-2021-45325 2022-02-08 13h36 +00:00 Server Side Request Forgery (SSRF) vulneraility exists in Gitea before 1.7.0 using the OpenID URL.
7.5
High
CVE-2020-28991 2020-11-23 23h29 +00:00 Gitea 0.9.99 through 1.12.x before 1.12.6 does not prevent a git protocol path that specifies a TCP port number and also contains newlines (with URL encoding) in ParseRemoteAddr in modules/auth/repo_form.go.
9.8
Critical
CVE-2020-14144 2020-10-16 11h02 +00:00 The git hook feature in Gitea 1.1.0 through 1.12.5 might allow for authenticated remote code execution in customer environments where the documentation was not understood (e.g., one viewpoint is that the dangerousness of this feature should be documented immediately above the ENABLE_GIT_HOOKS line in the config file). NOTE: The vendor has indicated this is not a vulnerability and states "This is a functionality of the software that is limited to a very limited subset of accounts. If you give someone the privilege to execute arbitrary code on your server, they can execute arbitrary code on your server. We provide very clear warnings to users around this functionality and what it provides.
7.2
High
CVE-2020-13246 2020-05-20 15h04 +00:00 An issue was discovered in Gitea through 1.11.5. An attacker can trigger a deadlock by initiating a transfer of a repository's ownership from one organization to another.
7.5
High
CVE-2019-1010261 2019-07-18 14h30 +00:00 Gitea 1.7.0 and earlier is affected by: Cross Site Scripting (XSS). The impact is: Attacker is able to have victim execute arbitrary JS in browser. The component is: go-get URL generation - PR to fix: https://github.com/go-gitea/gitea/pull/5905. The attack vector is: victim must open a specifically crafted URL. The fixed version is: 1.7.1 and later.
6.1
Medium
CVE-2019-11576 2019-04-27 23h40 +00:00 Gitea before 1.8.0 allows 1FA for user accounts that have completed 2FA enrollment. If a user's credentials are known, then an attacker could send them to the API without requiring the 2FA one-time password.
9.8
Critical
CVE-2019-11229 2019-04-13 13h07 +00:00 models/repo_mirror.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 mishandles mirror repo URL settings, leading to remote code execution.
8.8
High
CVE-2019-11228 2019-04-13 13h07 +00:00 repo/setting.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 does not validate the form.MirrorAddress before calling SaveAddress.
7.5
High
CVE-2019-1000002 2019-02-04 20h00 +00:00 Gitea version 1.6.2 and earlier contains a Incorrect Access Control vulnerability in Delete/Edit file functionallity that can result in the attacker deleting files outside the repository he/she has access to. This attack appears to be exploitable via the attacker must get write access to "any" repository including self-created ones.. This vulnerability appears to have been fixed in 1.6.3, 1.7.0-rc2.
6.5
Medium
CVE-2018-18926 2018-11-04 05h00 +00:00 Gitea before 1.5.4 allows remote code execution because it does not properly validate session IDs. This is related to session ID handling in the go-macaron/session code for Macaron.
9.8
Critical
CVE-2018-1000803 2018-10-08 15h00 +00:00 Gitea version prior to version 1.5.1 contains a CWE-200 vulnerability that can result in Exposure of users private email addresses. This attack appear to be exploitable via Watch a repository to receive email notifications. Emails received contain the other recipients even if they have the email set as private. This vulnerability appears to have been fixed in 1.5.1.
5.3
Medium
CVE-2018-15192 2018-08-08 02h00 +00:00 An SSRF vulnerability in webhooks in Gitea through 1.5.0-rc2 and Gogs through 0.11.53 allows remote attackers to access intranet services.
8.6
High