gssproxy up to 0.8.2 gp_workers.c gp_worker_main cond_mutex locking ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in gssproxy up to 0.8.2. Affected by this vulnerability is the function gp_worker_main of the file gp_workers.c. This manipulation of the argument cond_mutex causes an unknown weakness.
This vulnerability is registered as CVE-2020-12658. No exploit is available.
The actual existence of this vulnerability is currently in question.
It is advisable to upgrade the affected component.
Details
A vulnerability has been found in gssproxy up to 0.8.2 (Firewall Software) and classified as problematic. Affected by this vulnerability is the function gp_worker_main of the file gp_workers.c. The manipulation of the argument cond_mutex with an unknown input leads to a unknown weakness. The CWE definition for the vulnerability is CWE-667. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. The impact remains unknown. The summary by CVE is:
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.
The weakness was published 12/31/2020. It is possible to read the advisory at pagure.io. This vulnerability is known as CVE-2020-12658. Technical details of the vulnerability are known, but there is no available exploit.
The real existence of this vulnerability is still doubted at the moment.
Upgrading to version 0.8.3 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at pagure.io. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: LockingCWE: CWE-667
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: gssproxy 0.8.3
Patch: pagure.io
Timeline
12/31/2020 🔍12/31/2020 🔍
08/04/2024 🔍
Sources
Advisory: pagure.ioStatus: Confirmed
Disputed: 🔍
CVE: CVE-2020-12658 (🔍)
GCVE (CVE): GCVE-0-2020-12658
GCVE (VulDB): GCVE-100-167035
Entry
Created: 12/31/2020 10:44Updated: 08/04/2024 14:54
Changes: 12/31/2020 10:44 (40), 05/31/2024 12:40 (19), 08/04/2024 14:54 (22)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.