dbcve.org
Axeda AgentApplication · Ptc

CVE-2022-25251

CRITICAL · 9.8 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 →
100/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
When connecting to a certain port Axeda agent (All versions) and Axeda Desktop Server for Windows (All versions) may allow an attacker to send certain XML messages to a specific port without proper authentication. Successful exploitation of this vulnerability could allow a remote unauthenticated attacker to read and modify the affected product’s configuration.

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

Axeda agent and Axeda Desktop Server for Windows contain a vulnerability in a specific network port where XML messages can be received without authentication. An unauthenticated remote attacker can exploit this to read and modify the product's configuration, leading to potential full system compromise.

MitigationImplement proper authentication and authorization checks for all XML messages received on the affected port. Consider network segmentation to limit exposure and apply vendor-provided patches or updates when available.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 if Axeda agent or server is installed
    Check for Axeda installation directories (commonly in Program Files or Program Files (x86)) or look for 'Axeda' in installed programs via Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
    Affected if Axeda Agent or Axeda Desktop Server is found on the system
  2. Determine installed version of Axeda product
    Check the version information of the axeda.exe or axeda desktop server executable, typically found in the installation directory, or check the Windows Registry under the Axeda uninstall key for the DisplayVersion value
    Affected if Version is below 6.9.1 for Agent or below 6.9.215 for Desktop Server
  3. Identify if vulnerable network service is running
    Use netstat or PowerShell Get-NetTCPConnection to identify listening ports associated with Axeda processes (look for the process executable name in tasklist or taskmgr)
    Affected if The Axeda service is listening on any network port
  4. Verify if authentication is enabled on the XML service port
    Inspect the Axeda configuration files (typically .xml or .config files in the installation directory) for authentication settings related to the network listener service
    Affected if Authentication is disabled or not enforced on the XML message listener port
  5. Check network exposure of the service
    Review firewall rules and network configuration to determine if the Axeda port is accessible from untrusted networks or the internet
    Affected if The service port is exposed to untrusted network segments or the internet

A system is affected if it runs Axeda Agent version below 6.9.1 or Desktop Server version below 6.9.215 with the XML message listener port accessible over the network and authentication not enforced on that port.

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

Implement proper authentication and authorization checks for all XML messages received on the affected port. Consider network segmentation to limit exposure and apply vendor-provided patches or updates when available.

Recommended fix Moderate confidence

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

  1. Identify the installed Axeda Agent or Axeda Desktop Server version on the system
  2. If running Axeda Agent version < 6.9.1, download and install Axeda Agent version 6.9.1 or later
  3. If running Axeda Desktop Server version < 6.9.215, download and install Axeda Desktop Server version 6.9.215 or later
  4. After upgrade, verify the service is running correctly
  5. Confirm the specific port mentioned in the vulnerability is now properly authenticating XML message requests
  6. Test that configuration read/write operations require proper authentication

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

Fix this in Axeda Agent Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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