Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-65083: CWE-295 Improper Certificate Validation in Tinexta Infocert GoSign Desktop

0
Low
VulnerabilityCVE-2025-65083cvecve-2025-65083cwe-295
Published: Mon Nov 17 2025 (11/17/2025, 00:00:00 UTC)
Source: CVE Database V5
Vendor/Project: Tinexta Infocert
Product: GoSign Desktop

Description

GoSign Desktop through 2.4.1 disables TLS certificate validation when configured to use a proxy server. This can be problematic if the GoSign Desktop user selects an arbitrary proxy server without consideration of whether outbound HTTPS connections from the proxy server to Internet servers succeed even for untrusted or invalid server certificates. In this scenario (which is outside of the product's design objectives), integrity protection could be bypassed. In typical cases of a proxy server for outbound HTTPS traffic from an enterprise, those connections would not succeed. (Admittedly, the usual expectation is that a client application is configured to trust an enterprise CA and does not set SSL_VERIFY_NONE.) Also, it is of course unsafe to place ~/.gosign in the home directory of an untrusted user and then have other users execute downloaded files.

AI-Powered Analysis

AILast updated: 11/17/2025, 16:16:51 UTC

Technical Analysis

CVE-2025-65083 identifies an improper certificate validation vulnerability (CWE-295) in Tinexta Infocert's GoSign Desktop software versions up to 2.4.1. The core issue arises when GoSign Desktop is configured to use a proxy server for outbound HTTPS connections. In this configuration, the software disables TLS certificate validation, meaning it does not verify the authenticity or trustworthiness of server certificates presented through the proxy. This behavior can be exploited if a user configures the application to use an arbitrary or malicious proxy server that accepts or forwards HTTPS connections even with invalid or untrusted certificates. Under such circumstances, an attacker controlling the proxy could intercept or manipulate communications, bypassing integrity protections that TLS normally provides. The vulnerability does not affect confidentiality directly but can allow integrity bypass, potentially enabling tampering with signed data or communications. The attack vector is local (AV:L), requiring the attacker to influence proxy settings or have local access to the client environment. The attack complexity is high (AC:H), as it depends on specific proxy configurations and user choices. No privileges or user interaction are required once the proxy is set. The vulnerability is rated low severity with a CVSS 3.1 score of 3.2, reflecting limited impact and exploitation difficulty. Additionally, the advisory notes unsafe practices such as placing the ~/.gosign directory in untrusted user home directories, which could lead to execution of malicious files by other users, compounding risk. No known exploits are reported in the wild, and no patches are currently linked, indicating the need for cautious configuration and monitoring.

Potential Impact

For European organizations, especially those using Tinexta Infocert's GoSign Desktop for digital signatures and document authentication, this vulnerability could undermine the integrity of signed documents if exploited. While confidentiality is not directly impacted, the ability to bypass certificate validation can allow attackers to inject or alter data without detection, potentially invalidating trust in digital signatures. This is particularly critical in sectors relying on legally binding electronic signatures such as finance, legal, and government services. The risk is heightened in environments where proxy servers are used for outbound HTTPS traffic and where users might configure proxies without strict validation policies. However, the low CVSS score and high attack complexity suggest that widespread exploitation is unlikely without insider knowledge or control over proxy infrastructure. The vulnerability also highlights the importance of secure user environment management, as improper file permissions could lead to privilege escalation or code execution. Overall, the impact is moderate but could have serious consequences in high-assurance environments.

Mitigation Recommendations

1. Avoid configuring GoSign Desktop to use untrusted or arbitrary proxy servers. Ensure that proxy servers are managed and trusted within the enterprise network. 2. Verify and enforce TLS certificate validation settings in GoSign Desktop configurations, ensuring SSL_VERIFY_NONE or equivalent disabling of certificate checks is not set. 3. Implement strict network policies that prevent proxy servers from accepting or forwarding HTTPS connections with invalid or untrusted certificates. 4. Secure user home directories by restricting access permissions to the ~/.gosign directory, preventing untrusted users from placing or executing malicious files. 5. Educate users on the risks of configuring proxy settings and the importance of using trusted network infrastructure. 6. Monitor network traffic for unusual proxy usage or certificate validation bypass attempts. 7. Coordinate with Tinexta Infocert for updates or patches addressing this vulnerability once available. 8. Conduct regular security audits of client configurations and proxy server policies to ensure compliance with best practices.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-11-17T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 691b46c6bf18c64a4b2b8190

Added to database: 11/17/2025, 4:01:10 PM

Last enriched: 11/17/2025, 4:16:51 PM

Last updated: 11/17/2025, 8:25:57 PM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats