CVE-2025-34324
Infocert Gosign vulnerability
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.
Affected products
Gosign. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Infocert Gosign runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- www.ush.it/2025/11/14/multiple-vulnerabilities-gosign-desktop-remote-code-execution/ · Exploit
- www.ush.it/2025/11/14/vulnerabilita-multiple-gosign-desktop-esecuzione-remota-codice-arbit · Exploit
- www.vulncheck.com/advisories/gosign-desktop-insecure-update-mechanism-rce · Third Party Advisory
- infocert.digital/consumer/gosign-suite/
- nvd.nist.gov/vuln/detail/CVE-2025-34324
- cve.org/CVERecord?id=CVE-2025-34324
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.