CVE-2022-25250
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 · uneditedWhen connecting to a certain port Axeda agent (All versions) and Axeda Desktop Server for Windows (All versions) may allow an attacker to send a certain command to a specific port without authentication. Successful exploitation of this vulnerability could allow a remote unauthenticated attacker to shut down a specific service.
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 · moderate confidenceThe Axeda agent and Axeda Desktop Server for Windows contain an authentication bypass vulnerability where a specific port accepts commands without requiring authentication. An attacker can send a specific command to this port to shut down a critical service, resulting in denial of service. The vulnerability is exploitable remotely without any privileges or user interaction.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.9.1< 6.9.215CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Identify if Axeda software is installedCheck Windows installed programs list or look for Axeda-related processes in Task Manager. Common process names include AxedaAgent, AxedaDesktopServer, or eRemote. Use 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' or check Program Files directories for Axeda folders.Affected if PTC Axeda Agent or Axeda Desktop Server is found on the system
-
Check installed Axeda versionLocate the version information from the installed software, typically found in the About dialog of the application, in the Windows registry under the Axeda uninstall key, or in the application's installation directory. Compare the version number to the affected ranges: Axeda Agent < 6.9.1 or Axeda Desktop Server < 6.9.215.Affected if The installed version is lower than 6.9.1 for Axeda Agent or lower than 6.9.215 for Axeda Desktop Server
-
Determine if Axeda service is runningOpen Services.msc and look for Axeda-related services, or use command 'Get-Service | Where-Object {$_.DisplayName -like "*Axeda*"}' to list running Axeda services.Affected if The Axeda Agent or Axeda Desktop Server service is running and accepting network connections
-
Verify network exposure of Axeda portsUse 'netstat -an | findstr LISTENING' to identify listening ports, or run a port scan against the local host to find ports associated with Axeda services. Check firewall rules to determine if these ports are exposed to untrusted networks.Affected if The Axeda service port is accessible from untrusted network segments without authentication requirements
A system is affected if it runs PTC Axeda Agent version lower than 6.9.1 or Axeda Desktop Server version lower than 6.9.215, with the service running and network-accessible to untrusted users.
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.
dbcve · scoped6.9.16.9.215
Restrict network access to the affected Axeda ports using firewall rules or network segmentation to prevent unauthorized access. If available, apply vendor patches or consider upgrading to a secure alternative solution.
Axeda Agent: upgrade to version 6.9.1 or later; Axeda Desktop Server: upgrade to version 6.9.215 or later
- 1. Identify which Axeda products are deployed in your environment (Axeda Agent and/or Axeda Desktop Server).
- 2. Check the current version of each installed product using the system's version information or management console.
- 3. For Axeda Agent installations: upgrade to version 6.9.1 or later.
- 4. For Axeda Desktop Server installations: upgrade to version 6.9.215 or later.
- 5. Obtain the updated software from PTC's official support portal or authorized distribution channels.
- 6. Test the upgrade in a non-production environment first to verify compatibility.
- 7. Apply the upgrade to production systems following your organization's change management process.
- 8. Verify the service is running correctly after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25250 — 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-2022-25250 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