Skip to content
Fencer Intel
critical 9.8

CVE-2020-12658 json

gssproxy (aka gss-proxy) before 0.8.3 does not unlock cond_mutex before pthread exit in gp_worker_main() in gp_workers.c.

published 5y ago modified 4mo ago also EUVD-2020-4957

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

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.

Patch / fix

  • gssproxy_project gssproxy 0.8.3
  • gssproxy Debian 14, Debian 13, Debian 12 0.8.4-1

debian advisories DEBIAN-CVE-2020-12658

  • gssproxy SLES for SAP 12 SP5, SLES 12 SP5 0.8.2-4.5.1
  • gssproxy SLE Module for Basesystem 15 SP2 0.8.2-3.6.1

suse advisories SUSE-SU-2021:1030-1SUSE-SU-2021:1029-1

  • gssproxy openSUSE Leap 15.2 0.8.2-lp152.2.3.1

opensuse advisories openSUSE-SU-2021:0531-1

Is CVE-2020-12658 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-12658 updated cvss 0.0

gssproxy: not unlocking cond_mutex before pthread exit in gp_worker_main() in gp_workers.c

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.77% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.