CVE-2025-34324
Nov. 19, 2025, 7:14 p.m.
7.0
Medium
Description
GoSign Desktop versions 2.4.0 and earlier use an unsigned update manifest for distributing application updates. The manifest contains package URLs and SHA-256 hashes but is not digitally signed, so its authenticity relies solely on the underlying TLS channel. In affected versions, TLS certificate validation can be disabled when a proxy is configured, allowing an attacker who can intercept network traffic to supply a malicious update manifest and corresponding package with a matching hash. This can cause the client to download and install a tampered update, resulting in arbitrary code execution with the privileges of the GoSign Desktop user on Windows and macOS, or with elevated privileges on some Linux deployments. A local attacker who can modify proxy settings may also abuse this behavior to escalate privileges by forcing installation of a crafted update.
Product(s) Impacted
| Product | Versions |
|---|---|
| gosing_desktop |
|
| gosing_desktop |
|
Weaknesses
Common security weaknesses mapped to this vulnerability.
CWE-347
Improper Verification of Cryptographic Signature
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
References
Tags
CVSS Score
CVSS Data - 4.0
- Attack Vector: LOCAL
- Attack Complexity: LOW
- Attack Requirements: NONE
- Privileges Required: LOW
- User Interaction: PASSIVE
- Scope:
- Confidentiality Impact: HIGH
- Integrity Impact: HIGH
- Availability Impact: HIGH
- Exploit Maturity: NOT_DEFINED
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Timeline
Published: Nov. 18, 2025, 5:16 p.m.
Last Modified: Nov. 19, 2025, 7:14 p.m.
Last Modified: Nov. 19, 2025, 7:14 p.m.
Status : Awaiting Analysis
CVE has been marked for Analysis. Normally once in this state the CVE will be analyzed by NVD staff within 24 hours.
More infoSource
disclosure@vulncheck.com
*Disclaimer: Some vulnerabilities do not have an associated CPE. To enhance the data, we use AI to infer CPEs based on CVE details. This is an automated process and might not always be accurate.