dbcve.org
Automation License ManagerApplication · Siemens

CVE-2022-43513

HIGH · 7.5 CVSS v3.1 Published 2023-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A 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 components allow to rename license files with user chosen input without authentication. This could allow an unauthenticated remote attacker to rename and move files as SYSTEM user.

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

The vulnerability exists in Automation License Manager V5/V6 and TeleControl Server Basic V3 components. An unauthenticated remote attacker can provide user-controlled input to rename and move license files on the system. Since the affected service runs with SYSTEM privileges, this allows the attacker to rename and relocate files to arbitrary locations on the filesystem.

MitigationApply vendor-supplied patches: upgrade Automation License Manager V6 to V6.0 SP9 Upd4 or later, and TeleControl Server Basic V3 to V3.1.2 or later. For V5 which is end-of-life, migrate to a supported version. Implement network segmentation and restrict external access to the affected services.

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
Automation License ManagerApplication
Affected:= 5.0.0= 5.1= 5.2= 5.3= 5.3.4.4= 6.0= 6.0.1= 6.0.8= 6.0.9

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Locate installed Automation License Manager
    Check for Siemens Automation License Manager installation by searching common installation directories (typically C:\Program Files\Siemens\Automation License Manager or C:\Program Files (x86)\Siemens\Automation License Manager) and verify the presence of ALM.exe or similar executable files.
    Affected if The software is installed and the version matches any of these: 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
  2. Check TeleControl Server Basic installation
    Search for TeleControl Server Basic installation directories (typically under C:\Program Files\Siemens\ or C:\Program Files (x86)\Siemens\) and look for TcServerBasic or related executable files.
    Affected if The software is installed and is version 3.x (specifically affected versions prior to 3.1.2)
  3. Verify installed version numbers
    Right-click on the main executable (ALM.exe for Automation License Manager) and select Properties, then check the Details tab for the File Version. Alternatively, open the program and navigate to Help > About to view the version information.
    Affected if The reported version matches any of the affected versions listed in the CVE (5.0.0, 5.1, 5.2, 5.3, 5.3.4.4, 6.0, 6.0.1, 6.0.8, 6.0.9 for ALM; V3 versions prior to 3.1.2 for TeleControl Server Basic)
  4. Confirm service is running and listening
    Open Services.msc and look for Siemens Automation License Manager service or similar Siemens license management services. Use netstat -an to check if the service is listening on any network ports (typical ports may include 4410, 4411, or similar).
    Affected if The service is running and exposed on network ports accessible to untrusted users
  5. Assess network exposure
    Review firewall rules and binding addresses for the license manager service. Check if the service is bound to 0.0.0.0 or external network interfaces rather than only localhost (127.0.0.1).
    Affected if The service port is accessible from untrusted network segments or the internet

You are affected if either Siemens Automation License Manager (versions 5.0.0 through 6.0.9) or TeleControl Server Basic V3 (prior to 3.1.2) is installed, running, and network-accessible to unauthenticated 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches: upgrade Automation License Manager V6 to V6.0 SP9 Upd4 or later, and TeleControl Server Basic V3 to V3.1.2 or later. For V5 which is end-of-life, migrate to a supported version. Implement network segmentation and restrict external access to the affected services.

Recommended fix High confidence

Automation License Manager V6.0 SP9 Upd4 or later; TeleControl Server Basic V3.1.2 or later

  1. 1. Identify the installed product: Automation License Manager V5, V6, or TeleControl Server Basic V3
  2. 2. For Automation License Manager V5 (all versions): No fix available; upgrade to Automation License Manager V6.0 SP9 Upd4 or later
  3. 3. For Automation License Manager V6 (versions < V6.0 SP9 Upd4): Upgrade to version V6.0 SP9 Upd4 or later
  4. 4. For TeleControl Server Basic V3 (versions < V3.1.2): Upgrade to version V3.1.2 or later
  5. 5. After upgrade, verify the vulnerability is resolved by confirming file rename operations now require proper authentication
Caveat For V5 users: migrating to V6 may require license reconfiguration; test in staging before production deployment

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

Fix this in Automation License Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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