CVE-2020-12658 — Improper Locking in Project Gssproxy

CWE-667 — Improper Locking6 documents5 sources
Severity
9.8CRITICALNVD
EPSS
0.6%
top 31.24%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
3
Gssproxy Project GssproxyDebian LinuxDebian Gssproxy
Timeline
PublishedDec 31
Latest updateMay 24

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 vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitability: 3.9 | Impact: 5.9

Affected Packages2 packages

Also affects: Debian Linux 9.0

Patches

Patch: github.com ↗Patch: github.com ↗

🔴Vulnerability Details

3
GHSA
GHSA-p2qg-cv6r-5429: gssproxy (aka gss-proxy) before 0↗2022-05-24
▶
OSV
CVE-2020-12658: ** DISPUTED ** gssproxy (aka gss-proxy) before 0↗2020-12-31
▶
OSV
CVE-2020-12658: gssproxy (aka gss-proxy) before 0↗2020-12-31
▶

📋Vendor Advisories

2
Red Hat
gssproxy: not unlocking cond_mutex before pthread exit in gp_worker_main() in gp_workers.c↗2020-12-31
▶
Debian
CVE-2020-12658: gssproxy - gssproxy (aka gss-proxy) before 0.8.3 does not unlock cond_mutex before pthread ...↗2020
▶
CVE-2020-12658 — Improper Locking in Project Gssproxy | cvebase