dbcve.org
Axeda AgentApplication · Ptc

CVE-2022-25252

HIGH · 7.5 CVSS v3.1 Published 2022-03-16
Fix available
A fix is available. Upgrade to 6.9.1 / 6.9.215 or later.
See remediation →
84/100
Remediation priority · High
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
When connecting to a certain port Axeda agent (All versions) and Axeda Desktop Server for Windows (All versions) when receiving certain input throws an exception. Services using said function do not handle the exception. Successful exploitation of this vulnerability could allow a remote unauthenticated attacker to crash the affected product.

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 confidence

This is a denial-of-service vulnerability in Axeda agent and Axeda Desktop Server for Windows. When an unauthenticated remote attacker connects to a specific port and sends specially crafted input, the service throws an unhandled exception that crashes the affected product.

MitigationApply available patches from the vendor. If no patch exists, implement network-level filtering to restrict access to the vulnerable port and add exception handling around the affected function.

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
Axeda AgentApplication
Affected:< 6.9.1
Axeda Desktop ServerApplication
Affected:< 6.9.215

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
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 checks

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

  1. Identify installed Axeda products
    Check Windows Programs and Features (appwiz.cpl) or registry for installed Ptc Axeda Agent or Axeda Desktop Server. Look for Axeda-related services in Services.msc
    Affected if Either Axeda Agent or Axeda Desktop Server is present on the system
  2. Determine Axeda Agent version
    Right-click the installed Axeda Agent in Programs and Features and select Properties, or query the registry under HKLM\SOFTWARE\PTC\Axeda\Agent for Version value
    Affected if Version is lower than 6.9.1 (e.g., 6.9.0, 6.8.x, etc.)
  3. Determine Axeda Desktop Server version
    Right-click the installed Axeda Desktop Server in Programs and Features and select Properties, or query the registry under HKLM\SOFTWARE\PTC\Axeda\DesktopServer for Version value
    Affected if Version is lower than 6.9.215 (e.g., 6.9.0, 6.8.x, etc.)
  4. Identify exposed Axeda service port
    Run netstat -an | findstr LISTENING to find ports in listening state. Axeda typically uses port 4424 for agent communications, but verify against your environment documentation
    Affected if The Axeda service port (commonly 4424) is bound to 0.0.0.0 or an external-facing IP and is accessible from untrusted networks

You are affected if Axeda Agent version < 6.9.1 or Axeda Desktop Server version < 6.9.215 is installed AND the service port is accessible to unauthenticated remote attackers.

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
Upgrade available Upgrade to 6.9.1 / 6.9.215 or later
Fixed in 6.9.16.9.215
Interim mitigation

Apply available patches from the vendor. If no patch exists, implement network-level filtering to restrict access to the vulnerable port and add exception handling around the affected function.

Recommended fix High confidence

Axeda Agent to version 6.9.1 or later; Axeda Desktop Server to version 6.9.215 or later

  1. Identify the current version of Axeda Agent or Axeda Desktop Server installed in your environment
  2. Navigate to the PTC support portal or Axeda product download page
  3. Download Axeda Agent version 6.9.1 or later for the agent component
  4. Download Axeda Desktop Server version 6.9.215 or later for the Desktop Server component
  5. Test the upgrade in a non-production environment first
  6. Apply the upgrade to production systems following standard change management procedures
  7. Verify the service is running correctly after upgrade

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

Fix this in Axeda Agent Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25252 — 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-2022-25252 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