CVE-2020-12658
gssproxy (aka gss-proxy) before 0.8.3 does not unlock cond_mutex before pthread exit in gp_worker_main() in gp_workers.c.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (1.68%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
gssproxy (aka gss-proxy) before 0.8.3 does not unlock cond_mutex before pthread exit in gp_worker_main() in gp_workers.c. NOTE: An upstream comment states "We are already on a shutdown path when running the code in question, so a DoS there doesn't make any sense, and there has been no additional information provided us (as upstream) to indicate why this would be a problem.
- CVSS 3.1
- 9.8 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 1.68% probability · 76th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-667
- Affected
- gssproxy project/gssproxy · debian/debian linux
- Source
- cve@mitre.org
References
- https://github.com/gssapi/gssproxy/commit/cb761412e299ef907f22cd7c4146d50c8a792003Patch, Third Party Advisory
- https://github.com/gssapi/gssproxy/compare/v0.8.2...v0.8.3Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2021/01/msg00004.htmlMailing List, Third Party Advisory
- https://pagure.io/gssproxy/c/cb761412e299ef907f22cd7c4146d50c8a792003?branch=masterThird Party Advisory
- https://github.com/gssapi/gssproxy/commit/cb761412e299ef907f22cd7c4146d50c8a792003Patch, Third Party Advisory
- https://github.com/gssapi/gssproxy/compare/v0.8.2...v0.8.3Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2021/01/msg00004.htmlMailing List, Third Party Advisory
- https://pagure.io/gssproxy/c/cb761412e299ef907f22cd7c4146d50c8a792003?branch=masterThird Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.