SCA-2026-0015
Vulnerability from csaf_sick - Published: 2026-10-15 13:00 - Updated: 2026-10-15 13:00| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Sick_Safetyscanners_Base CPP Driver 1.0.5
SICK AG / SICK Open Source Solutions / Sick_Safetyscanners_Base CPP Driver
|
1.0.5 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Sick_Safetyscanners_Base CPP Driver <= 1.0.4
SICK AG / SICK Open Source Solutions / Sick_Safetyscanners_Base CPP Driver
|
<= 1.0.4 |
Vendor Fix
|
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Sick_Safetyscanners_Base CPP Driver 1.0.5
SICK AG / SICK Open Source Solutions / Sick_Safetyscanners_Base CPP Driver
|
1.0.5 |
{
"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 out-of-bounds read vulnerability exists in the open-source repository sick_safetyscanners_base (https://github.com/SICKAG/sick_safetyscanners_base), a standalone C++ driver library for SICK safety laser scanners. A specially crafted network packet could cause the library to read data beyond the bounds of the received buffer. If exploited, this vulnerability could potentially affect the availability of applications using the affected library. SICK recommends applying the defined remediations for this vulnerability.",
"title": "summary"
},
{
"category": "general",
"text": "As general security measures, SICK recommends minimizing network exposure of the devices, restricting network access and following recommended security practices in order to run the devices in a protected IT environment.",
"title": "General Security Measures"
},
{
"category": "general",
"text": "SICK performs vulnerability classification by using the CVSS scoring system (*CVSS v3.1*). The environmental score is dependent on the customer\u2019s environment and can affect the overall CVSS score. SICK recommends that customers individually evaluate the environmental score to achieve final scoring.",
"title": "Vulnerability Classification"
}
],
"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-0015.json"
},
{
"summary": "Affected Repository",
"url": "https://github.com/SICKAG/sick_safetyscanners_base"
}
],
"title": "Vulnerability Affecting Sick_Safetyscanners_Base CPP Driver",
"tracking": {
"current_release_date": "2026-10-15T13:00:00.000Z",
"generator": {
"date": "2026-10-08T08:01:20.469Z",
"engine": {
"name": "Secvisogram",
"version": "2.6.13"
}
},
"id": "sca-2026-0015",
"initial_release_date": "2026-10-15T13:00:00.000Z",
"revision_history": [
{
"date": "2026-10-15T13:00:00.000Z",
"number": "1",
"summary": "Initial version"
}
],
"status": "final",
"version": "1"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "\u003c= 1.0.4",
"product": {
"name": "Sick_Safetyscanners_Base CPP Driver \u003c= 1.0.4",
"product_id": "CSAFPID-51000"
}
},
{
"category": "product_version",
"name": "1.0.5",
"product": {
"name": "Sick_Safetyscanners_Base CPP Driver 1.0.5",
"product_id": "CSAFPID-52000"
}
}
],
"category": "product_name",
"name": "Sick_Safetyscanners_Base CPP Driver"
}
],
"category": "product_family",
"name": "SICK Open Source Solutions"
}
],
"category": "vendor",
"name": "SICK AG"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2026-101290",
"cwe": {
"id": "CWE-125",
"name": "Out-of-bounds Read"
},
"notes": [
{
"audience": "all",
"category": "summary",
"text": "A remote attacker may send a specially crafted network packet that causes the affected application to perform an out-of-bounds memory read due to insufficient validation of packet length. This may result in an application crash and a denial-of-service condition.",
"title": "Summary"
}
],
"product_status": {
"fixed": [
"CSAFPID-52000"
],
"known_affected": [
"CSAFPID-51000"
],
"recommended": [
"CSAFPID-52000"
]
},
"remediations": [
{
"category": "vendor_fix",
"date": "2026-10-01T13:51:11.858Z",
"details": "Users are recommended to upgrade to version 1.0.5.",
"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-101290"
}
]
}
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.