SCA-2026-0018
Vulnerability from csaf_sick - Published: 2026-11-18 14:47 - Updated: 2026-11-18 14:47| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
SICK sick_scan_xd 3.10.0
SICK AG / SICK Open Source Solutions / sick_scan_xd
|
3.10.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
SICK sick_scan_xd < 3.10.0
SICK AG / SICK Open Source Solutions / sick_scan_xd
|
< 3.10.0 |
Vendor Fix
|
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
SICK sick_scan_xd 3.10.0
SICK AG / SICK Open Source Solutions / sick_scan_xd
|
3.10.0 |
{
"document": {
"acknowledgments": [
{
"names": [
"kta1kri"
],
"summary": "reporting this issue in a coordinated manner",
"urls": [
"https://github.com/kta1kri"
]
}
],
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE",
"url": "https://www.first.org/tlp/"
}
},
"lang": "en-US",
"notes": [
{
"category": "summary",
"text": "An integer overflow vulnerability exists in the open-source repository sick_scan_xd (https://github.com/SICKAG/sick_scan_xd), a ROS 2 driver library and software development kit for SICK LiDAR and RADAR devices. A specially crafted network packet could cause an integer overflow during packet size validation, potentially bypassing boundary checks and resulting in out-of-bounds reads. If exploited, this vulnerability could affect the availability of applications using the affected library. SICK recommends applying the defined remediation for this vulnerability.",
"title": "Summary"
},
{
"category": "description",
"text": "If exploited, the vulnerability could potentially allow an unauthenticated attacker to compromise the availability of the product.",
"title": "Impact"
},
{
"category": "description",
"text": "As general security measures, SICK recommends minimizing network exposure of the devices, restricting network access, and following recommended security practices in order to operate the devices in a protected IT environment.",
"title": "Mitigation"
},
{
"category": "description",
"text": "SICK recommends ensuring that the product operates within a secure environment.",
"title": "Remediation"
}
],
"publisher": {
"category": "vendor",
"contact_details": "psirt@sick.de",
"issuing_authority": "SICK AG issues and issues in EHS products (when related to the Endress+Hauser SICK (EHS) joint venture).",
"name": "SICK PSIRT",
"namespace": "https://www.sick.com/psirt"
},
"references": [
{
"summary": "SICK PSIRT Security Advisories",
"url": "https://www.sick.com/psirt"
},
{
"summary": "SICK Operating Guidelines",
"url": "https://www.sick.com/media/docs/9/19/719/special_information_sick_operating_guidelines_cybersecurity_by_sick_en_im0106719.pdf"
},
{
"summary": "ICS-CERT recommended practices on Industrial Security",
"url": "https://www.cisa.gov/resources-tools/resources/ics-recommended-practices"
},
{
"summary": "CVSS v3.1 Calculator",
"url": "https://www.first.org/cvss/calculator/3.1"
},
{
"category": "self",
"summary": "The canonical URL",
"url": "https://www.sick.com/.well-known/csaf/white/2026/sca-2026-0018.json"
},
{
"summary": "Affected Repository",
"url": "https://github.com/SICKAG/sick_scan_xd"
}
],
"title": "Vulnerability Affecting sick_scan_xd Driver",
"tracking": {
"current_release_date": "2026-11-18T14:47:00.000Z",
"generator": {
"date": "2026-11-10T09:40:47.851Z",
"engine": {
"name": "Secvisogram",
"version": "2.6.19"
}
},
"id": "sca-2026-0018",
"initial_release_date": "2026-11-18T14:47:00.000Z",
"revision_history": [
{
"date": "2026-11-18T14:47:00.000Z",
"number": "1",
"summary": "Initial version"
}
],
"status": "final",
"version": "1"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "\u003c 3.10.0",
"product": {
"name": "SICK sick_scan_xd \u003c 3.10.0",
"product_id": "CSAFPID-51000"
}
},
{
"category": "product_version",
"name": "3.10.0",
"product": {
"name": "SICK sick_scan_xd 3.10.0",
"product_id": "CSAFPID-52000"
}
}
],
"category": "product_name",
"name": "sick_scan_xd"
}
],
"category": "product_family",
"name": "SICK Open Source Solutions"
}
],
"category": "vendor",
"name": "SICK AG"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2026-123123",
"cwe": {
"id": "CWE-190",
"name": "Integer Overflow or Wraparound"
},
"notes": [
{
"audience": "all",
"category": "summary",
"text": "An attacker that is able to send a crafted network packet to the affected component may trigger an integer overflow during module size validation. This may cause insufficient bounds checking and result in out-of-bounds memory reads, potentially leading to a denial of service condition due to process termination.",
"title": "Summary"
}
],
"product_status": {
"fixed": [
"CSAFPID-52000"
],
"known_affected": [
"CSAFPID-51000"
],
"recommended": [
"CSAFPID-52000"
]
},
"remediations": [
{
"category": "vendor_fix",
"details": "Users are recommended to upgrade to version 3.10.0.\n",
"product_ids": [
"CSAFPID-51000"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"environmentalScore": 7.5,
"environmentalSeverity": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"temporalScore": 7.5,
"temporalSeverity": "HIGH",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"products": [
"CSAFPID-51000"
]
}
],
"title": "CVE-2026-123123"
}
]
}
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.