SSA-103653
Vulnerability from csaf_siemens - Published: 2024-09-10 00:00 - Updated: 2025-05-13 00:00| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Automation License Manager V5
Siemens / Automation License Manager V5
|
vers:all/* |
Mitigation
Mitigation
No Fix Planned
|
|
|
Automation License Manager V6.0
Siemens / Automation License Manager V6.0
|
All versions < V6.0 SP12 Upd3 |
Mitigation
Mitigation
Vendor Fix
fix
|
|
|
Automation License Manager V6.2
Siemens / Automation License Manager V6.2
|
All versions < V6.2 Upd3 |
Mitigation
Mitigation
Vendor Fix
fix
|
{
"document": {
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"text": "Disclosure is not limited. (TLPv2: TLP:CLEAR)",
"tlp": {
"label": "WHITE"
}
},
"lang": "en",
"notes": [
{
"category": "summary",
"text": "A vulnerability was identified in the Automation License Manager software that could be triggered by sending specially crafted packets to port\n4410/tcp of an affected system. This could cause a denial-of-service preventing legitimate users from using the system.\n\nSiemens has released new versions for several affected products and recommends to update to the latest versions. Siemens recommends specific countermeasures for products where fixes are not, or not yet available.",
"title": "Summary"
},
{
"category": "general",
"text": "As a general security measure, Siemens strongly recommends to protect network access to devices with appropriate mechanisms. In order to operate the devices in a protected IT environment, Siemens recommends to configure the environment according to Siemens\u0027 operational guidelines for Industrial Security (Download: \nhttps://www.siemens.com/cert/operational-guidelines-industrial-security), and to follow the recommendations in the product manuals.\nAdditional information on Industrial Security by Siemens can be found at: https://www.siemens.com/industrialsecurity",
"title": "General Recommendations"
},
{
"category": "general",
"text": "For further inquiries on security vulnerabilities in Siemens products and solutions, please contact the Siemens ProductCERT: https://www.siemens.com/cert/advisories",
"title": "Additional Resources"
},
{
"category": "legal_disclaimer",
"text": "The use of Siemens Security Advisories is subject to the terms and conditions listed on: https://www.siemens.com/productcert/terms-of-use.",
"title": "Terms of Use"
}
],
"publisher": {
"category": "vendor",
"contact_details": "productcert@siemens.com",
"name": "Siemens ProductCERT",
"namespace": "https://www.siemens.com"
},
"references": [
{
"category": "self",
"summary": "SSA-103653: Denial-of-Service Vulnerability in Automation License Manager - HTML Version",
"url": "https://cert-portal.siemens.com/productcert/html/ssa-103653.html"
},
{
"category": "self",
"summary": "SSA-103653: Denial-of-Service Vulnerability in Automation License Manager - CSAF Version",
"url": "https://cert-portal.siemens.com/productcert/csaf/ssa-103653.json"
}
],
"title": "SSA-103653: Denial-of-Service Vulnerability in Automation License Manager",
"tracking": {
"current_release_date": "2025-05-13T00:00:00Z",
"generator": {
"engine": {
"name": "Siemens ProductCERT CSAF Generator",
"version": "1"
}
},
"id": "SSA-103653",
"initial_release_date": "2024-09-10T00:00:00Z",
"revision_history": [
{
"date": "2024-09-10T00:00:00Z",
"legacy_version": "1.0",
"number": "1",
"summary": "Publication Date"
},
{
"date": "2025-05-13T00:00:00Z",
"legacy_version": "1.1",
"number": "2",
"summary": "Added fix for Automation License Manager V6.0"
}
],
"status": "interim",
"version": "2"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "vers:all/*",
"product": {
"name": "Automation License Manager V5",
"product_id": "1"
}
}
],
"category": "product_name",
"name": "Automation License Manager V5"
},
{
"branches": [
{
"category": "product_version_range",
"name": "All versions \u003c V6.0 SP12 Upd3",
"product": {
"name": "Automation License Manager V6.0",
"product_id": "2"
}
}
],
"category": "product_name",
"name": "Automation License Manager V6.0"
},
{
"branches": [
{
"category": "product_version_range",
"name": "All versions \u003c V6.2 Upd3",
"product": {
"name": "Automation License Manager V6.2",
"product_id": "3"
}
}
],
"category": "product_name",
"name": "Automation License Manager V6.2"
}
],
"category": "vendor",
"name": "Siemens"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2024-44087",
"cwe": {
"id": "CWE-190",
"name": "Integer Overflow or Wraparound"
},
"notes": [
{
"category": "summary",
"text": "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.",
"title": "Summary"
}
],
"product_status": {
"known_affected": [
"1",
"2",
"3"
]
},
"remediations": [
{
"category": "mitigation",
"details": "On the Automation License Manager settings menu disable \"Allow Remote Connections\"",
"product_ids": [
"1",
"2",
"3"
]
},
{
"category": "mitigation",
"details": "If remote connections are needed, limit remote access to port 4410/tcp to trusted systems only",
"product_ids": [
"1",
"2",
"3"
]
},
{
"category": "no_fix_planned",
"details": "Currently no fix is planned",
"product_ids": [
"1"
]
},
{
"category": "vendor_fix",
"details": "Update to V6.0 SP12 Upd3 or later version",
"product_ids": [
"2"
],
"url": "https://support.industry.siemens.com/cs/ww/en/view/114358/"
},
{
"category": "vendor_fix",
"details": "Update to V6.2 Upd3 or later version",
"product_ids": [
"3"
],
"url": "https://support.industry.siemens.com/cs/ww/en/view/114358/"
}
],
"scores": [
{
"cvss_v3": {
"baseScore": 8.6,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H",
"version": "3.1"
},
"products": [
"1",
"2",
"3"
]
}
],
"title": "CVE-2024-44087"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.