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.
Metrics
Affected Vendors & Products
References
History
Wed, 31 Dec 2025 02:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Infocert
Infocert gosign |
|
| CPEs | cpe:2.3:a:infocert:gosign:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Infocert
Infocert gosign |
|
| Metrics |
cvssV3_1
|
Thu, 20 Nov 2025 10:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tinexta Infocert
Tinexta Infocert gosign Desktop |
|
| Vendors & Products |
Tinexta Infocert
Tinexta Infocert gosign Desktop |
Tue, 18 Nov 2025 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 18 Nov 2025 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | GoSign Desktop < 2.4.1 Insecure Update Mechanism RCE | |
| Weaknesses | CWE-347 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: VulnCheck
Published: 2025-11-18T16:33:05.469Z
Updated: 2025-11-18T18:24:11.777Z
Reserved: 2025-04-15T19:15:22.585Z
Link: CVE-2025-34324
Updated: 2025-11-18T18:24:01.521Z
Status : Analyzed
Published: 2025-11-18T17:16:00.923
Modified: 2025-12-31T02:19:33.927
Link: CVE-2025-34324
No data.