CVE-2022-43514
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 · uneditedA vulnerability has been identified in Automation License Manager V5 (All versions), Automation License Manager V6 (All versions < V6.0 SP9 Upd4), TeleControl Server Basic V3 (All versions < V3.1.2). The affected component does not correctly validate the root path on folder related operations, allowing to modify files and folders outside the intended root directory. This could allow an unauthenticated remote attacker to execute file operations of files outside of the specified root folder. Chained with CVE-2022-43513 this could allow Remote Code Execution.
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 confidencePath traversal vulnerability in Automation License Manager V5/V6 and TeleControl Server Basic V3 allows unauthenticated remote attackers to modify files and folders outside the intended root directory due to improper validation of root paths on folder-related operations. When chained with CVE-2022-43513, this can lead to remote code execution.
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= 5.0.0= 5.1= 5.2= 5.3= 5.3.4.4= 6.0= 6.0.1= 6.0.8= 6.0.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Siemens Automation License Manager versionCheck the installed version of Siemens Automation License Manager. On Windows, this can typically be found in Add/Remove Programs, or check the file version of the executable (often in C:\Program Files\Siemens\Automation License Manager or similar installation directory).Affected if The installed version matches any of the following: 5.0.0, 5.1, 5.2, 5.3, 5.3.4.4, 6.0, 6.0.1, 6.0.8, or 6.0.9.
-
Identify installed TeleControl Server Basic versionCheck the installed version of TeleControl Server Basic. This is typically found in the software inventory, installation directory, or product-specific license/About information.Affected if The installed version is V3.x and matches the affected version range for TeleControl Server Basic V3.
-
Verify if folder-related operations are exposedReview the service configuration and network exposure of the Automation License Manager or TeleControl Server Basic. The vulnerability affects folder-related operations (create folder, delete folder, folder listing). Determine if these operations are accessible via network interfaces.Affected if Folder-related operations in the license management or server service are network-accessible without authentication.
-
Check network accessibility of the serviceReview firewall rules, network segmentation, and exposed interfaces for the Automation License Manager service ports. The vulnerability allows unauthenticated remote exploitation.Affected if The service is exposed to unauthenticated network attackers (e.g., not restricted to localhost or properly segmented trusted networks).
You are affected if Automation License Manager version 5.0.0-6.0.9 or TeleControl Server Basic V3 is installed and the folder-related operations are network-accessible to unauthenticated 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 · scopedUpgrade to patched versions (Automation License Manager V6 >= V6.0 SP9 Upd4, TeleControl Server Basic V3 >= V3.1.2) and implement network segmentation to limit exposure to unauthenticated attackers.
Automation License Manager V6.0 SP9 Upd4 or later; TeleControl Server Basic V3.1.2 or later
- Identify the currently installed version of Automation License Manager or TeleControl Server Basic using the system's software management interface
- For Automation License Manager V6: Upgrade to version V6.0 SP9 Upd4 or later
- For TeleControl Server Basic V3: Upgrade to version V3.1.2 or later
- For Automation License Manager V5: This version has no patch available; migrate to Automation License Manager V6 and apply the V6.0 SP9 Upd4 update
- After upgrading, verify the installation by checking the product version in the Siemens software management console
- Restart the affected services to ensure the patched components are fully loaded
- Confirm the path traversal vulnerability is resolved by verifying file operations are restricted to intended root directories
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43514 — 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-43514 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