x-crypto up to 0.30.x on Go ServerConfig.PublicKeyCallback excessive reliance on global variables
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in x-crypto up to 0.30.x on Go. It has been declared as problematic. Impacted is the function ServerConfig.PublicKeyCallback. Such manipulation leads to excessive reliance on global variables.
This vulnerability is referenced as CVE-2024-45337. No exploit is available.
It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in x-crypto up to 0.30.x on Go. Affected by this issue is the function ServerConfig.PublicKeyCallback. The manipulation with an unknown input leads to a excessive reliance on global variables vulnerability. Using CWE to declare the problem leads to CWE-1108. The code is structured in a way that relies too much on using
or setting global variables throughout various points in the code, instead of
preserving the associated information in a narrower, more local
context. The impact remains unknown. CVE summarizes:
Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.
The advisory is available at go.dev. This vulnerability is handled as CVE-2024-45337 since 08/27/2024. Technical details are known, but there is no available exploit.
The vulnerability scanner Nessus provides a plugin with the ID 213037 (Fedora 41 : golang-x-crypto (2024-c33c95804e)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 0.31.0 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (213037) and CERT Bund (WID-SEC-2024-3690). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Affected
- Amazon Linux 2
- Red Hat Enterprise Linux
- Fedora Linux
- Ubuntu Linux
- SUSE Linux
- SUSE openSUSE
- IBM MQ
- Open Source Gitea
- Red Hat OpenShift
- IBM Storage Scale
- Splunk Splunk Enterprise
Product
Name
Version
- 0.1
- 0.2
- 0.3
- 0.4
- 0.5
- 0.6
- 0.7
- 0.8
- 0.9
- 0.10
- 0.11
- 0.12
- 0.13
- 0.14
- 0.15
- 0.16
- 0.17
- 0.18
- 0.19
- 0.20
- 0.21
- 0.22
- 0.23
- 0.24
- 0.25
- 0.26
- 0.27
- 0.28
- 0.29
- 0.30
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.2
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.1
CNA 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: 🔍
Exploiting
Class: Excessive reliance on global variablesCWE: CWE-1108
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 |
Nessus ID: 213037
Nessus Name: Fedora 41 : golang-x-crypto (2024-c33c95804e)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: x-crypto 0.31.0
Timeline
08/27/2024 🔍12/11/2024 🔍
12/11/2024 🔍
06/20/2026 🔍
Sources
Advisory: go.devStatus: Confirmed
CVE: CVE-2024-45337 (🔍)
GCVE (CVE): GCVE-0-2024-45337
GCVE (VulDB): GCVE-100-287930
CERT Bund: WID-SEC-2024-3690 - Gitea: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen
Entry
Created: 12/11/2024 20:38Updated: 06/20/2026 05:58
Changes: 12/11/2024 20:38 (53), 12/16/2024 12:17 (2), 02/01/2025 00:35 (12), 06/20/2026 05:58 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.