CVE-2020-12658Not scoredCWE-667

CVE-2020-12658: Gssproxy Project vulnerability

Gssproxy Project · Gssproxy

Affected: Gssproxy Project · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.8%probability of exploitation in the next 30 days

78th percentile

050100

Higher than 78% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Locking · Race Conditions
Published: December 2020
Band: Possible (1 to 10%), December 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-12658 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.