CVE-2022-25249
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) (disregarding Axeda agent v6.9.2 and v6.9.3) is vulnerable to directory traversal, which could allow a remote unauthenticated attacker to obtain file system read access via web server..
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 confidenceAxeda agent and Axeda Desktop Server for Windows contain a directory traversal vulnerability in their web server component. A remote unauthenticated attacker can exploit this by using '../' sequences in HTTP requests to traverse the file system and read sensitive files anywhere on the host where the process has read permissions.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Axeda installation on the systemSearch for Axeda installation directories in common locations such as 'C:\Program Files\PTC\Axeda' or 'C:\Program Files (x86)\PTC\Axeda'. Also check for service entries named 'Axeda Agent' or 'Axeda Desktop Server' in Windows Services (services.msc).Affected if Axeda Agent or Axeda Desktop Server is installed on the Windows host
-
Determine the installed versionCheck the version of the installed Axeda software. Look for version information in the executable properties (right-click the main .exe file and view Properties > Details), in the Windows Registry under HKLM\SOFTWARE\PTC\Axeda or HKLM\SOFTWARE\Wow6432Node\PTC\Axeda, or in an 'about' or 'version' file within the installation directory.Affected if The installed version is below 6.9.1 for Axeda Agent or below 6.9.215 for Axeda Desktop Server
-
Verify the web server component is runningCheck if the Axeda web server service is active. In Windows, run 'services.msc' and look for a service related to Axeda (such as 'Axeda Agent' or 'Axeda Desktop Server') with status 'Running'. Alternatively, use command 'netstat -an | findstr LISTENING' to check for ports typically used by Axeda (commonly port 80, 443, or 3147).Affected if The Axeda web server component is enabled and actively listening for HTTP connections
-
Confirm the vulnerability is exploitableThe vulnerability is present if the web server is running and the version is in the affected range. The directory traversal can be tested by sending an HTTP GET request with '../' sequences to the web server (for example: GET /../../windows/win.ini HTTP/1.1). A response containing file contents indicates the vulnerability exists.Affected if The web server responds with file contents when using '../' traversal sequences in HTTP requests
A user is affected if they have Ptc Axeda Agent version below 6.9.1 or Ptc Axeda Desktop Server version below 6.9.215 running with the web server component enabled.
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
Apply vendor patches if available; otherwise implement input validation/restricted path access on the web server, restrict network access to the affected service, or disable the web server component if not required.
Axeda Agent: 6.9.1 or later | Axeda Desktop Server: 6.9.215 or later
- 1. Identify the currently installed Axeda Agent version by checking the installation or consulting inventory systems
- 2. Identify the currently installed Axeda Desktop Server version by checking the installation or consulting inventory systems
- 3. For Axeda Agent: Upgrade to version 6.9.1 or later (note: versions 6.9.2 and 6.9.3 also address this vulnerability)
- 4. For Axeda Desktop Server: Upgrade to version 6.9.215 or later
- 5. Obtain the updated installer from PTC's official support portal at www.ptc.com
- 6. Test the upgrade in a non-production environment before deploying to production
- 7. After upgrade, verify the web server functionality and confirm the vulnerability is remediated
- 8. Schedule the upgrade during a planned maintenance window following organizational change management procedures
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25249 — 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-25249 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