dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-34179

HIGH · 8.7 CVSS v4.0 Published 2025-12-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NetSupport Manager < 14.12.0001 contains an unauthenticated SQL injection vulnerability in its Connectivity Server/Gateway HTTPS request handling. The server evaluates request URIs using an unsanitized SQLite query against the FileLinks table in gateway.db. By injecting SQL through the LinkName/URI value, a remote attacker can control the FileName field used by the server to read and return files from disk, resulting in arbitrary local file disclosure.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unauthenticated SQL injection in NetSupport Manager's Connectivity Server/Gateway allows remote attackers to inject malicious SQL through the LinkName/URI parameter in HTTPS requests. The unsanitized query against the FileLinks table in gateway.db permits attackers to control the FileName field, enabling arbitrary local file disclosure from the server's disk.

MitigationUpgrade NetSupport Manager to version 14.12.0001 or later to obtain the patched build. If immediate patching is not feasible, restrict network access to the Connectivity Server/Gateway using firewall rules to limit exposure to trusted IPs only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if NetSupport Manager Connectivity Server/Gateway is installed
    Look for NetSupport Manager installation on the system. On Windows, check Program Files for 'NetSupport' folder or check Windows Services for 'NetSupport Manager Gateway' or 'Connectivity Server' services.
    Affected if The NetSupport Manager Connectivity Server/Gateway component is present on the system.
  2. Verify the gateway.db database file exists
    Search for the file gateway.db in the NetSupport installation directory, typically found in the 'gateway' or 'data' subfolder.
    Affected if The gateway.db file exists, indicating the vulnerable database component is present.
  3. Determine the installed NetSupport Manager version
    Check the installed version of NetSupport Manager. On Windows, right-click the NetSupport Manager executable in the installation folder, select Properties, and view the Details tab for version information. Alternatively, check the Windows Services description for the Gateway service.
    Affected if The installed version is prior to 14.12.0001, as this is the patched version.
  4. Check if the Connectivity Server/Gateway service is running
    Open Windows Services (services.msc) and look for 'NetSupport Manager Gateway' or 'NetSupport Connectivity Server' service. Verify if the service status is Running.
    Affected if The Connectivity Server/Gateway service is enabled and running, exposing the vulnerable HTTPS listener.
  5. Inspect network listening ports
    Run 'netstat -an | findstr 443' or use 'netsh interface tcp show global' to check if port 443 (HTTPS) is open and listening, which indicates the Gateway HTTPS interface is active.
    Affected if Port 443 is listening and bound to the NetSupport Gateway service, making the SQL injection vulnerability accessible over the network.

The environment is affected if NetSupport Manager Connectivity Server/Gateway is installed with a version prior to 14.12.0001 and the Gateway HTTPS service is running and network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade NetSupport Manager to version 14.12.0001 or later to obtain the patched build. If immediate patching is not feasible, restrict network access to the Connectivity Server/Gateway using firewall rules to limit exposure to trusted IPs only.

Recommended fix High confidence

NetSupport Manager 14.12.0001 or later

  1. 1. Identify all deployed instances of NetSupport Manager Connectivity Server/Gateway.
  2. 2. Check the current version of each installation (typically found in the application properties or about dialog).
  3. 3. Download NetSupport Manager version 14.12.0001 or later from the official vendor site or your licensed download location.
  4. 4. Review the vendor release notes for any migration requirements or注意事项 before upgrading.
  5. 5. Back up the existing gateway.db database and configuration files.
  6. 6. Apply the upgrade to all affected Connectivity Server/Gateway installations.
  7. 7. Verify the upgrade was successful by confirming the version number matches 14.12.0001 or higher.
  8. 8. Test that the Gateway functionality operates normally after the upgrade.
Caveat Review vendor release notes - minor version upgrades typically maintain backward compatibility but test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34179 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34179 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data