dbcve.org
Axeda AgentApplication · Ptc

CVE-2022-25248

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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) supplies the event log of the 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 confidence

The Axeda agent and Axeda Desktop Server for Windows expose event log contents of the specific service when an attacker connects to a certain port, resulting in unintended information disclosure.

MitigationRestrict network access to the affected port using firewall rules or network segmentation to prevent unauthorized connections, and contact the vendor for patched versions if 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 Desktop Server is installed
    Check Windows services for 'Axeda' or 'PTC' entries, or look for Axeda installation directories (commonly in C:\Program Files\PTC or C:\Program Files (x86)\PTC). Use 'services.msc' or PowerShell: Get-Service | Where-Object {$_.DisplayName -like '*Axeda*' -or $_.DisplayName -like '*PTC*'}
    Affected if No Axeda or PTC services are found - not affected. If services exist, proceed to version check.
  2. Determine the installed Axeda Agent version
    Check the version of the installed Axeda agent executable. Common locations: C:\Program Files\PTC\Axeda\Agent\ or check the service executable properties. Use PowerShell: Get-Item 'C:\Program Files\PTC\Axeda\Agent\*exe' | Select-Object Name, VersionInfo
    Affected if Version is lower than 6.9.1 - the environment is affected.
  3. Determine the installed Axeda Desktop Server version
    Check the version of the installed Axeda Desktop Server executable. Look in installation directories like C:\Program Files\PTC\Axeda\DesktopServer\ or check the Desktop Server service properties.
    Affected if Version is lower than 6.9.215 - the environment is affected.
  4. Check network exposure of the Axeda service port
    Identify which port the Axeda service listens on (check registry under HKLM\SYSTEM\CurrentControlSet\Services\Axeda* or service configuration). Use netstat to check listening ports: netstat -an | findstr 'LISTENING' then correlate with Axeda service port.
    Affected if The Axeda service port is exposed to untrusted networks (Internet or external systems) - the information disclosure vulnerability is reachable.

The environment is affected if either Axeda Agent version is below 6.9.1 or Desktop Server version is below 6.9.215, AND the service port is network-accessible to untrusted users.

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

Restrict network access to the affected port using firewall rules or network segmentation to prevent unauthorized connections, and contact the vendor for patched versions if available.

Recommended fix Moderate confidence

Axeda Agent >= 6.9.1, Axeda Desktop Server >= 6.9.215

  1. Upgrade Axeda Agent to version 6.9.1 or later
  2. Upgrade Axeda Desktop Server to version 6.9.215 or later
  3. After upgrading, verify that the service no longer exposes event log information when connecting to the affected port

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

Fix this in Axeda Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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