Tinexta InfoCert GoSign Desktop up to 2.4.0 on Windows signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Tinexta InfoCert GoSign Desktop up to 2.4.0 on Windows. It has been rated as critical. This affects an unknown function. This manipulation causes signature verification. This vulnerability is tracked as CVE-2025-34324. The attack is restricted to local execution. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability classified as critical was found in Tinexta InfoCert GoSign Desktop up to 2.4.0 on Windows. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a signature verification vulnerability. The CWE definition for the vulnerability is CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was disclosed by Pasquale Fiorillo, Francesco Ongaro and Marco Lunardi. The advisory is shared at ush.it. This vulnerability is known as CVE-2025-34324 since 04/15/2025. The exploitation appears to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.
Upgrading to version 2.4.1 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.6
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.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: 🔍
Exploiting
Class: Signature verificationCWE: CWE-347 / CWE-345
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
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: GoSign Desktop 2.4.1
Timeline
04/15/2025 CVE reserved11/18/2025 Advisory disclosed
11/18/2025 VulDB entry created
12/31/2025 VulDB entry last update
Sources
Advisory: ush.itResearcher: Pasquale Fiorillo, Francesco Ongaro, Marco Lunardi
Status: Confirmed
CVE: CVE-2025-34324 (🔒)
GCVE (CVE): GCVE-0-2025-34324
GCVE (VulDB): GCVE-100-332857
Entry
Created: 11/18/2025 20:25Updated: 12/31/2025 04:55
Changes: 11/18/2025 20:25 (67), 12/31/2025 04:55 (10)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.