** DISPUTED ** 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."
References
Link | Resource |
---|---|
https://pagure.io/gssproxy/c/cb761412e299ef907f22cd7c4146d50c8a792003?branch=master | Third Party Advisory |
https://github.com/gssapi/gssproxy/commit/cb761412e299ef907f22cd7c4146d50c8a792003 | Patch Third Party Advisory |
https://github.com/gssapi/gssproxy/compare/v0.8.2...v0.8.3 | Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2021/01/msg00004.html | Mailing List Third Party Advisory |
Information
Published : 2020-12-30 17:15
Updated : 2021-02-08 05:46
NVD link : CVE-2020-12658
Mitre link : CVE-2020-12658
JSON object : View
CWE
CWE-667
Improper Locking
Products Affected
gssproxy_project
- gssproxy
debian
- debian_linux