dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-49849

HIGH · 7.8 CVSS v3.1 Published 2024-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 SIMATIC S7-PLCSIM V16 (All versions), SIMATIC S7-PLCSIM V17 (All versions), SIMATIC STEP 7 Safety V16 (All versions), SIMATIC STEP 7 Safety V17 (All versions < V17 Update 9), SIMATIC STEP 7 Safety V18 (All versions), SIMATIC STEP 7 Safety V19 (All versions < V19 Update 4), SIMATIC STEP 7 V16 (All versions), SIMATIC STEP 7 V17 (All versions < V17 Update 9), SIMATIC STEP 7 V18 (All versions), SIMATIC STEP 7 V19 (All versions < V19 Update 4), SIMATIC WinCC Unified V16 (All versions), SIMATIC WinCC Unified V17 (All versions < V17 Update 9), SIMATIC WinCC Unified V18 (All versions), SIMATIC WinCC Unified V19 (All versions < V19 Update 4), SIMATIC WinCC V16 (All versions), SIMATIC WinCC V17 (All versions < V17 Update 9), SIMATIC WinCC V18 (All versions), SIMATIC WinCC V19 (All versions < V19 Update 4), SIMOCODE ES V16 (All versions), SIMOCODE ES V17 (All versions), SIMOCODE ES V18 (All versions), SIMOCODE ES V19 (All versions), SIMOTION SCOUT TIA V5.4 (All versions), SIMOTION SCOUT TIA V5.5 (All versions), SIMOTION SCOUT TIA V5.6 (All versions < V5.6 SP1 HF7), SINAMICS Startdrive V16 (All versions), SINAMICS Startdrive V17 (All versions), SINAMICS Startdrive V18 (All versions), SINAMICS Startdrive V19 (All versions), SIRIUS Safety ES V17 (TIA Portal) (All versions), SIRIUS Safety ES V18 (TIA Portal) (All versions), SIRIUS Safety ES V19 (TIA Portal) (All versions), SIRIUS Soft Starter ES V17 (TIA Portal) (All versions), SIRIUS Soft Starter ES V18 (TIA Portal) (All versions), SIRIUS Soft Starter ES V19 (TIA Portal) (All versions), TIA Portal Cloud V16 (All versions), TIA Portal Cloud V17 (All versions), TIA Portal Cloud V18 (All versions), TIA Portal Cloud V19 (All versions < V5.2.1.1). Affected products do not properly sanitize user-controllable input when parsing log files. This could allow an attacker to cause a type confusion and execute arbitrary code within the affected application.

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

Multiple Siemens TIA Portal and related industrial software products contain a vulnerability in log file parsing where user-controllable input is not properly sanitized, leading to type confusion that can be exploited for arbitrary code execution.

MitigationApply available vendor updates: V17 Update 9, V19 Update 4, V5.6 SP1 HF7, or V5.2.1.1 depending on the product. Until patched, restrict access to log files from untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Siemens TIA Portal version
    Open Windows Control Panel > Programs and Features, or check the installation directory (typically C:\Program Files\Siemens\Automation) for TIA Portal folders named by version (e.g., TIA Portal V17, TIA Portal V19). Right-click the software in Programs and Features and select 'Change' or 'Properties' to view the version number.
    Affected if The installed version matches V17, V18, V19, V5.6 SP1, or V5.2.1 (or falls within these version families without the noted security updates)
  2. Confirm exact version and patch level
    Launch TIA Portal and navigate to 'Help' > 'About TIA Portal' to see the full version string including Update or Hotfix level (e.g., V17 Update 9, V19 Update 4). Alternatively, check the program's 'Properties' > 'Details' tab for version information.
    Affected if The version is earlier than V17 Update 9, V19 Update 4, V5.6 SP1 HF7, or V5.2.1.1 for the respective product line
  3. Verify log file parsing functionality is present
    Locate the project's log files or logging configuration within TIA Portal (typically under 'Logs' or 'Diagnostic' folders in the project tree, or in the installation's 'Log' directory). Check if the software processes or can be configured to parse external log files.
    Affected if Log file parsing features are accessible and the software handles log files from any source (the vulnerability triggers when parsing untrusted log files)
  4. Check for third-party or external log file integration
    Review project settings and any configured log file paths or imports. Inspect whether the TIA Portal environment is configured to read log files from network locations, USB drives, or other external sources.
    Affected if The software is configured to import, read, or parse log files from untrusted or shared network sources

A defender is affected if Siemens TIA Portal or related industrial software is installed and the version predates the fixed releases (V17 Update 9, V19 Update 4, V5.6 SP1 HF7, or V5.2.1.1), with log file parsing functionality exposed to potentially untrusted input sources.

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 available vendor updates: V17 Update 9, V19 Update 4, V5.6 SP1 HF7, or V5.2.1.1 depending on the product. Until patched, restrict access to log files from untrusted sources.

Recommended fix High confidence

Product-specific: V17 Update 9, V19 Update 4, V5.6 SP1 HF7, or V5.2.1.1 depending on product line

  1. 1. Identify the specific affected product and version installed in your environment from the list: SIMATIC S7-PLCSIM, SIMATIC STEP 7 (including Safety), SIMATIC WinCC (including Unified), SIMOCODE ES, SIMOTION SCOUT TIA, SINAMICS Startdrive, SIRIUS Safety ES, SIRIUS Soft Starter ES, or TIA Portal Cloud.
  2. 2. Determine the current installed version of the affected product.
  3. 3. For SIMATIC STEP 7 V17, WinCC V17, WinCC Unified V17: Upgrade to V17 Update 9 or later.
  4. 4. For SIMATIC STEP 7 V19, WinCC V19, WinCC Unified V19, SIMATIC STEP 7 Safety V19: Upgrade to V19 Update 4 or later.
  5. 5. For SIMOTION SCOUT TIA V5.6: Upgrade to V5.6 SP1 HF7 or later.
  6. 6. For TIA Portal Cloud V19: Upgrade to V5.2.1.1 or later.
  7. 7. For all other products listed as 'All versions' with no specific patch mentioned (V16 variants, SIMOCODE ES, SINAMICS V16-V19, SIRIUS variants), contact Siemens customer support to obtain the fixed version or patch.
Caveat Review Siemens release notes for any compatibility or migration considerations before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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