dbcve.org
Telecontrol Server BasicApplication · Siemens

CVE-2024-44102

CRITICAL · 10.0 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 3.1.2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 PP TeleControl Server Basic 1000 to 5000 V3.1 (6NH9910-0AA31-0AE1) (All versions < V3.1.2.1 with redundancy configured), PP TeleControl Server Basic 256 to 1000 V3.1 (6NH9910-0AA31-0AD1) (All versions < V3.1.2.1 with redundancy configured), PP TeleControl Server Basic 32 to 64 V3.1 (6NH9910-0AA31-0AF1) (All versions < V3.1.2.1 with redundancy configured), PP TeleControl Server Basic 64 to 256 V3.1 (6NH9910-0AA31-0AC1) (All versions < V3.1.2.1 with redundancy configured), PP TeleControl Server Basic 8 to 32 V3.1 (6NH9910-0AA31-0AB1) (All versions < V3.1.2.1 with redundancy configured), TeleControl Server Basic 1000 V3.1 (6NH9910-0AA31-0AD0) (All versions < V3.1.2.1 with redundancy configured), TeleControl Server Basic 256 V3.1 (6NH9910-0AA31-0AC0) (All versions < V3.1.2.1 with redundancy configured), TeleControl Server Basic 32 V3.1 (6NH9910-0AA31-0AF0) (All versions < V3.1.2.1 with redundancy configured), TeleControl Server Basic 5000 V3.1 (6NH9910-0AA31-0AE0) (All versions < V3.1.2.1 with redundancy configured), TeleControl Server Basic 64 V3.1 (6NH9910-0AA31-0AB0) (All versions < V3.1.2.1 with redundancy configured), TeleControl Server Basic 8 V3.1 (6NH9910-0AA31-0AA0) (All versions < V3.1.2.1 with redundancy configured), TeleControl Server Basic Serv Upgr (6NH9910-0AA31-0GA1) (All versions < V3.1.2.1 with redundancy configured), TeleControl Server Basic Upgr V3.1 (6NH9910-0AA31-0GA0) (All versions < V3.1.2.1 with redundancy configured). The affected system allows remote users to send maliciously crafted objects. Due to insecure deserialization of user-supplied content by the affected software, an unauthenticated attacker could exploit this vulnerability by sending a maliciously crafted serialized object. This could allow the attacker to execute arbitrary code on the device with SYSTEM privileges.

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

This vulnerability in Siemens TeleControl Server Basic (V3.1) allows unauthenticated remote attackers to execute arbitrary code with SYSTEM privileges through insecure deserialization of maliciously crafted serialized objects. The flaw affects multiple server models (Basic 8 through 5000) when redundancy is configured, in versions prior to V3.1.2.1.

MitigationUpgrade all affected TeleControl Server Basic installations to version V3.1.2.1 or later. Since the vulnerability requires redundancy configuration to be exploitable, temporarily disabling redundancy during the upgrade process may be considered as a compensating control if immediate upgrading is not feasible.

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
Telecontrol Server BasicApplication
Affected:>= 3.1, < 3.1.2.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Verify TeleControl Server Basic is installed
    Locate the TeleControl Server Basic installation directory or check system services for 'Siemens TeleControl Server Basic' entry
    Affected if Product is not present on the system
  2. Determine installed software version
    Check the installed version through the product's About dialog, installation logs, or version information in the program directory
    Affected if Installed version is 3.1.x where x is less than 2.1 (i.e., version is >= 3.1 but < 3.1.2.1)
  3. Confirm redundancy configuration status
    Access the TeleControl Server Basic administration interface and navigate to redundancy settings, or inspect the configuration files for redundancy-related parameters
    Affected if Redundancy is enabled or configured on the affected version (this configuration is required for the vulnerability to be exploitable)

User is affected if TeleControl Server Basic V3.1 through V3.1.2.0 is installed with redundancy enabled or configured.

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 3.1.2.1 or later
Fixed in 3.1.2.1
Vendor patch cert-portal.siemens.com →
Interim mitigation

Upgrade all affected TeleControl Server Basic installations to version V3.1.2.1 or later. Since the vulnerability requires redundancy configuration to be exploitable, temporarily disabling redundancy during the upgrade process may be considered as a compensating control if immediate upgrading is not feasible.

Recommended fix High confidence

V3.1.2.1

  1. Identify the current installed version of TeleControl Server Basic by checking the system documentation or version information within the application
  2. Confirm whether redundancy is configured on the affected system, as only configurations with redundancy are vulnerable
  3. Schedule a maintenance window for the upgrade process
  4. Back up the current system configuration and any critical data before proceeding
  5. Obtain the fixed version V3.1.2.1 from the official Siemens support channels or cert-portal.siemens.com
  6. Upgrade the TeleControl Server Basic installation to version 3.1.2.1 following the vendor's upgrade documentation
  7. After upgrade, verify that the redundancy configuration is functioning correctly
  8. Confirm the installed version is now V3.1.2.1 or higher

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

Fix this in Telecontrol Server Basic Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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