CVE-2025-34164
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 · uneditedA heap-based buffer overflow vulnerability in NetSupport Manager 14.x versions prior to 14.12.0000 allows a remote, unauthenticated attacker to cause a denial of service (DoS) or execute arbitrary code.
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 confidenceNetSupport Manager versions 14.x prior to 14.12.0000 contain a heap-based buffer overflow vulnerability that can be exploited remotely by an unauthenticated attacker, potentially leading to denial of service or arbitrary code execution.
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:H/VA:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate NetSupport Manager installationCheck for NetSupport Manager installation directory (typically C:\Program Files\NetSupport\NetSupport Manager or C:\Program Files (x86)\NetSupport\NetSupport Manager) or look for the executable named pcic32.exe, nsm.exe, or similar NetSupport binaries.Affected if NetSupport Manager is installed on the system
-
Identify installed versionRetrieve the version number of the NetSupport Manager executable. Right-click the main executable file, select Properties, and check the Details tab for version information. Alternatively, query the Windows Registry under HKLM\SOFTWARE\NetSupport\NetSupport Manager for the Version value, or use 'wmic product where "name like 'NetSupport Manager'" get version' if available.Affected if The installed version is earlier than 14.12.0000
-
Verify service status and listening portsOpen Services (services.msc), locate the NetSupport Manager service, and verify its status. Use 'netstat -an' or a tool like TCPView to identify which ports the NetSupport Manager process is listening on (common ports include TCP 5405, 5406).Affected if The NetSupport Manager service is running and listening on network ports
-
Assess network exposureCheck firewall rules to determine if the NetSupport Manager service ports are exposed to untrusted networks. Use 'netsh advfirewall firewall show rule name=all' or examine inbound firewall rules. Verify whether the system is accessible from outside the local network.Affected if The NetSupport Manager service ports are accessible from untrusted or external network sources
A system is affected if NetSupport Manager is installed with a version lower than 14.12.0000 and the service is running and exposed to network connections.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade NetSupport Manager to version 14.12.0000 or later to remediate this vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34164 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-34164 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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