dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2024-44087

HIGH · 8.6 CVSS v3.1 Published 2024-09-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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.0 (All versions < V6.0 SP12 Upd3), Automation License Manager V6.2 (All versions < V6.2 Upd3). Affected applications do not properly validate certain fields in incoming network packets on port 4410/tcp. This could allow an unauthenticated remote attacker to cause an integer overflow and crash of the application. This denial of service condition could prevent legitimate users from using subsequent products that rely on the affected application for license verification.

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

Automation License Manager V5 and V6.x listening on TCP port 4410 fails to properly validate specific fields in incoming network packets, allowing an unauthenticated remote attacker to trigger an integer overflow that crashes the application and causes denial of service.

MitigationApply vendor patches: upgrade to V6.0 SP12 Upd3 or later, or V6.2 Upd3 or later. As a temporary workaround, restrict network access to port 4410/tcp.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 Automation License Manager is listening on port 4410/tcp
    Run 'netstat -an | grep 4410' or 'ss -tlnp | grep 4410' to confirm the service is bound and listening
    Affected if Port 4410/tcp is in LISTEN state and the service is exposed to network
  2. Identify the installed Automation License Manager version
    Check the product documentation or use 'swlist' (HP-UX), 'dpkg -l' (Linux), or the ALM GUI/SNMP to retrieve the version number
    Affected if Version is V5.x or V6.x before V6.0 SP12 Upd3 or V6.2 Upd3
  3. Compare installed version against fixed releases
    Review the version string obtained; fixed versions are V6.0 SP12 Upd3 and later, or V6.2 Upd3 and later
    Affected if Version is earlier than the fixed releases (V5 any version, V6.0 before SP12 Upd3, V6.2 before Upd3)
  4. Assess network exposure of the service
    Determine if port 4410 is reachable from untrusted networks or if firewall rules restrict access to trusted hosts only
    Affected if Port 4410 is accessible from untrusted network segments without filtering

You are affected if Automation License Manager V5 or V6.x (before V6.0 SP12 Upd3 or V6.2 Upd3) is running and listening on port 4410/tcp with network accessibility.

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 patches: upgrade to V6.0 SP12 Upd3 or later, or V6.2 Upd3 or later. As a temporary workaround, restrict network access to port 4410/tcp.

Recommended fix High confidence

Automation License Manager V6.0 SP12 Upd3 or higher; V6.2 Upd3 or higher; contact Siemens for V5 options

  1. 1. Identify the currently installed version of Automation License Manager (V5, V6.0, or V6.2)
  2. 2. For Automation License Manager V6.0: Upgrade to version V6.0 SP12 Upd3 or later
  3. 3. For Automation License Manager V6.2: Upgrade to version V6.2 Upd3 or later
  4. 4. For Automation License Manager V5: Contact Siemens directly for available patches or migration options to a supported version
  5. 5. After upgrading, verify the application runs on port 4410/tcp without crashes
  6. 6. Test that license verification functionality works correctly for downstream products
Caveat Upgrading major versions or service packs may require testing license compatibility with dependent applications

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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