CVE-2025-65083

3.2 LOW

📋 TL;DR

GoSign Desktop versions through 2.4.1 disable TLS certificate validation when configured to use a proxy server, allowing man-in-the-middle attacks that could bypass HTTPS integrity protection. This affects users who configure arbitrary proxy servers without proper certificate validation. The vulnerability primarily impacts users who place the application in untrusted environments or misconfigure proxy settings.

💻 Affected Systems

Products:
  • GoSign Desktop
Versions: through 2.4.1
Operating Systems: Windows, Linux, macOS
Default Config Vulnerable: ✅ No
Notes: Only vulnerable when configured to use a proxy server. The vulnerability requires specific proxy configuration to be exploitable.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker performing a man-in-the-middle attack could intercept and modify HTTPS traffic between GoSign Desktop and remote servers, potentially leading to credential theft, data manipulation, or malware delivery.

🟠

Likely Case

In enterprise environments with properly configured proxy servers and certificate authorities, the impact is minimal as connections would fail with invalid certificates. The most likely impact is in misconfigured or untrusted proxy scenarios.

🟢

If Mitigated

With proper enterprise proxy configuration and trusted certificate authorities, connections would fail for invalid certificates, preventing exploitation.

🌐 Internet-Facing: LOW with brief explanation
🏢 Internal Only: MEDIUM with brief explanation

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires man-in-the-middle position and specific proxy configuration. No public exploit code has been identified.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://www.firma.infocert.it/prodotti/gosign

Restart Required: No

Instructions:

Check vendor website for security updates. No specific patch version is mentioned in available references.

🔧 Temporary Workarounds

Avoid Untrusted Proxy Configuration

all

Do not configure GoSign Desktop to use arbitrary or untrusted proxy servers. Only use enterprise-approved proxy servers with proper certificate validation.

Secure Home Directory Configuration

linux

Ensure ~/.gosign directory is not accessible to untrusted users and other users cannot execute downloaded files from this location.

chmod 700 ~/.gosign
chown trusted_user:trusted_group ~/.gosign

🧯 If You Can't Patch

  • Configure GoSign Desktop to use only trusted enterprise proxy servers with proper certificate validation.
  • Implement network segmentation to prevent man-in-the-middle attacks between GoSign Desktop and proxy servers.

🔍 How to Verify

Check if Vulnerable:

Check GoSign Desktop version and proxy configuration settings. Versions 2.4.1 and earlier with proxy configuration are vulnerable.

Check Version:

gosign --version or check About menu in GUI

Verify Fix Applied:

Verify that TLS certificate validation is enabled when using proxy servers. Test HTTPS connections to servers with invalid certificates should fail.

📡 Detection & Monitoring

Log Indicators:

  • Failed TLS certificate validation attempts
  • Proxy connection errors with invalid certificates

Network Indicators:

  • HTTPS traffic to/from GoSign Desktop with invalid certificates
  • Unusual proxy server connections

SIEM Query:

source="gosign" AND (event="proxy_connection" OR event="tls_handshake") AND result="success" AND certificate_status="invalid"

🔗 References

📤 Share & Export