Skip to content

Gogs vulnerable to improper PAM authorization handling

High severity GitHub Reviewed Published Mar 12, 2022 in gogs/gogs • Updated Jun 30, 2023

Package

gomod gogs.io/gogs (Go)

Affected versions

< 0.12.5

Patched versions

0.12.5

Description

Impact

Expired PAM accounts and accounts with expired passwords are continued to be seen as valid. Installations use PAM as authentication sources are affected.

Patches

Expired PAM accounts and accounts with expired passwords are no longer being seen as valid. Users should upgrade to 0.12.5 or the latest 0.13.0+dev.

Workarounds

In addition to marking PAM accounts as expired, also disable/lock them. Running usermod -L <username> will add an exclamation mark to the password hash and would result in wrong passwords responses when trying to login.

References

https://huntr.dev/bounties/ea82cfc9-b55c-41fe-ae58-0d0e0bd7ab62/

For more information

If you have any questions or comments about this advisory, please post on gogs/gogs#6810.

References

@unknwon unknwon published to gogs/gogs Mar 12, 2022
Published to the GitHub Advisory Database Mar 14, 2022
Reviewed Mar 14, 2022
Last updated Jun 30, 2023

Severity

High

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
Low
Availability
None

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:L/A:N

EPSS score

0.183%
(57th percentile)

Weaknesses

CVE ID

CVE-2022-0871

GHSA ID

GHSA-gw5h-h6hj-f56g

Source code

Credits

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