# CVE-2024-22039: Memory corruption in Cerberus PRO EN Engineering Tool > Unauthenticated remote attackers can execute arbitrary code with root privileges via a stack-based buffer overflow in the network communication library. - **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 12 Mar 2024 - **Updated:** 16 Dec 2025 - **Also known as:** GHSA-p429-8j49-f6x5 ## What is CVE-2024-22039? CVE-2024-22039 is a critical memory corruption vulnerability in Siemens Cerberus PRO EN Engineering Tool, published on 12 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability has been identified in Cerberus PRO EN Engineering Tool (All versions < IP8), Cerberus PRO EN Fire Panel FC72x IP6 (All versions < IP6 SR3), Cerberus PRO EN Fire Panel FC72x IP7 (All versions < IP7 SR5), Cerberus PRO EN X200 Cloud Distribution IP7 (All versions < V3.0.6602), Cerberus PRO EN X200 Cloud Distribution IP8 (All versions < V4.0.5016), Cerberus PRO EN X300 Cloud Distribution IP7 (All versions < V3.2.6601), Cerberus PRO EN X300 Cloud Distribution IP8 (All versions < V4.2.5015), Cerberus PRO UL Compact Panel FC922/924 (All versions < MP4), Cerberus PRO UL Engineering Tool (All versions < MP4), Cerberus PRO UL X300 Cloud Distribution (All versions < V4.3.0001), Desigo Fire Safety UL Compact Panel FC2025/2050 (All versions < MP4), Desigo Fire Safety UL Engineering Tool (All versions < MP4), Desigo Fire Safety UL X300 Cloud Distribution (All versions < V4.3.0001), Sinteso FS20 EN Engineering Tool (All versions < MP8), Sinteso FS20 EN Fire Panel FC20 MP6 (All versions < MP6 SR3), Sinteso FS20 EN Fire Panel FC20 MP7 (All versions < MP7 SR5), Sinteso FS20 EN X200 Cloud Distribution MP7 (All versions < V3.0.6602), Sinteso FS20 EN X200 Cloud Distribution MP8 (All versions < V4.0.5016), Sinteso FS20 EN X300 Cloud Distribution MP7 (All versions < V3.2.6601), Sinteso FS20 EN X300 Cloud Distribution MP8 (All versions < V4.2.5015), Sinteso Mobile (All versions < V3.0.0). The network communication library in affected systems does not validate the length of certain X.509 certificate attributes which might result in a stack-based buffer overflow. This could allow an unauthenticated remote attacker to execute code on the underlying operating system with root privileges. Weakness: CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2024-22039? It affects 9 products. Products: Siemens Cerberus Pro en Engineering Tool, Siemens Cerberus Pro en Fire Panel Fc72x, Siemens Cerberus Pro en X200 Cloud Distribution, Siemens Cerberus Pro en X300 Cloud Distribution, Siemens Sinteso Fs20 en Engineering Tool, Siemens Sinteso Fs20 en Fire Panel Fc20, Siemens Sinteso Fs20 en X200 Cloud Distribution, Siemens Sinteso Fs20 en X300 Cloud Distribution, Siemens Sinteso Mobile. ## How do I fix CVE-2024-22039? No fix has been published for CVE-2024-22039 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-22039 being exploited? There is no known exploitation of CVE-2024-22039 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-22039 and fix it if it is affected. What it is: CVE-2024-22039 is a critical memory corruption vulnerability in Siemens Cerberus PRO EN Engineering Tool, published on 12 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-22039 in the wild and no public exploit code. Affected product: Siemens Cerberus PRO EN Engineering Tool. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-22039/ (Markdown: https://insights.sbomify.com/CVE-2024-22039/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-22039 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-22039 - OSV: https://osv.dev/vulnerability/CVE-2024-22039 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-22039/ Summaries are generated and may contain mistakes; the official description above is the record.