Skip to content

Gitea Allows 1FA Even for 2FA-Enrolled Accounts

Critical severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Apr 24, 2024

Package

gomod code.gitea.io/gitea (Go)

Affected versions

< 1.8.0

Patched versions

1.8.0

Description

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.

References

Published by the National Vulnerability Database Apr 28, 2019
Published to the GitHub Advisory Database May 24, 2022
Reviewed Apr 24, 2024
Last updated Apr 24, 2024

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.240%
(63rd percentile)

Weaknesses

CVE ID

CVE-2019-11576

GHSA ID

GHSA-3393-r4p5-vhqh

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.