ICSA-20-051-01
Vulnerability from csaf_cisa - Published: 2020-02-20 00:00 - Updated: 2020-02-20 00:00| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Automation Studio: Versions 2.7 3.0.71 3.0.80 3.0.81 3.0.90 4.0.x to 4.6.4 and 4.7.2
B&R Industrial Automation / Automation Studio
|
2.7 | 3.0.71 | 3.0.80 | 3.0.81 | 3.0.90 | >= 4.0.x | <= 4.6.4 | 4.7.2 |
Mitigation
Mitigation
Mitigation
Mitigation
Mitigation
fix
|
|
|
Automation Runtime: Versions 2.96 3.00 3.01 3.06 3.07 3.08 to 3.10 4.00 to 4.03 4.04 to 4.03 4.04 to 4.63 4.72 and above
B&R Industrial Automation / Automation Runtime
|
2.96 | 3.00 | 3.01 | 3.06 | 3.07 | >= 3.08 | <= 3.10 | >= 4.00 | <= 4.03 | >= 4.03 | <= 4.04 | >= 4.04 | <= 4.63 | >= 4.72 |
Mitigation
Mitigation
Mitigation
Mitigation
Mitigation
fix
|
{
"document": {
"acknowledgments": [
{
"names": [
"Yehuda Anikster",
"Amir Preminger"
],
"organization": "Claroty",
"summary": "reporting this vulnerability to CISA"
}
],
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"text": "Disclosure is not limited",
"tlp": {
"label": "WHITE"
}
},
"lang": "en-US",
"notes": [
{
"category": "general",
"text": "This CSAF advisory was extracted from unstructured data and may contain inaccuracies. If you notice any errors, please reach out to the designated contact at CISA CSAF: central@cisa.dhs.gov",
"title": "CISA Disclaimer"
},
{
"category": "summary",
"text": "Yehuda Anikster and Amir Preminger of Claroty reported this vulnerability to CISA.",
"title": "Summary"
},
{
"category": "other",
"text": "No known public exploits specifically target this vulnerability.",
"title": "Exploitability"
}
],
"publisher": {
"category": "coordinator",
"contact_details": "CISAservicedesk@cisa.dhs.gov",
"name": "CISA",
"namespace": "https://www.cisa.gov/"
},
"references": [
{
"category": "self",
"summary": "ICS Advisory ICSA-20-051-01 JSON",
"url": "https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/OT/white/2020/icsa-20-051-01.json"
},
{
"category": "self",
"summary": "ICS Advisory ICSA-20-051-01 Web Version",
"url": "https://www.cisa.gov/news-events/ics-advisories/icsa-20-051-01"
}
],
"title": "ICSA-20-051-01_B\u0026R Automation Studio and Automation Runtime",
"tracking": {
"current_release_date": "2020-02-20T00:00:00.000000Z",
"generator": {
"engine": {
"name": "CISA USCert CSAF Generator",
"version": "1"
}
},
"id": "ICSA-20-051-01",
"initial_release_date": "2020-02-20T00:00:00.000000Z",
"revision_history": [
{
"date": "2020-02-20T00:00:00.000000Z",
"legacy_version": "Initial",
"number": "1",
"summary": "ICSA-20-051-01 B\u0026R Automation Automation Studio and Automation Runtime"
}
],
"status": "final",
"version": "1"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "2.7 | 3.0.71 | 3.0.80 | 3.0.81 | 3.0.90 | \u003e= 4.0.x | \u003c= 4.6.4 | 4.7.2",
"product": {
"name": "Automation Studio: Versions 2.7 3.0.71 3.0.80 3.0.81 3.0.90 4.0.x to 4.6.4 and 4.7.2",
"product_id": "CSAFPID-0001"
}
}
],
"category": "product_name",
"name": "Automation Studio"
},
{
"branches": [
{
"category": "product_version_range",
"name": "2.96 | 3.00 | 3.01 | 3.06 | 3.07 | \u003e= 3.08 | \u003c= 3.10 | \u003e= 4.00 | \u003c= 4.03 | \u003e= 4.03 | \u003c= 4.04 | \u003e= 4.04 | \u003c= 4.63 | \u003e= 4.72",
"product": {
"name": "Automation Runtime: Versions 2.96 3.00 3.01 3.06 3.07 3.08 to 3.10 4.00 to 4.03 4.04 to 4.03 4.04 to 4.63 4.72 and above",
"product_id": "CSAFPID-0002"
}
}
],
"category": "product_name",
"name": "Automation Runtime"
}
],
"category": "vendor",
"name": "B\u0026R Industrial Automation"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2019-19108",
"cwe": {
"id": "CWE-285",
"name": "Improper Authorization"
},
"notes": [
{
"category": "summary",
"text": "The affected products are vulnerable to a weakness in SNMP service, which allows unauthenticated users to modify the configuration via the service.CVE-2019-19108 has been assigned to this vulnerability. A CVSS v3 base score of 9.4 has been calculated; the CVSS vector string is (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H).",
"title": "Summary"
}
],
"product_status": {
"known_affected": [
"CSAFPID-0001",
"CSAFPID-0002"
]
},
"references": [
{
"summary": "www.first.org",
"url": "https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H"
}
],
"remediations": [
{
"category": "mitigation",
"details": "B\u0026R reports product-technical reasons disallow the changing of SNMP credentials. To reduce risk from this vulnerability, the following Automation Studio versions disable the SNMP service by default in newly created AS projects:",
"product_ids": [
"CSAFPID-0001",
"CSAFPID-0002"
]
},
{
"category": "mitigation",
"details": "AS 4.6.5 (Planned release date: 2020-03-27) and higher",
"product_ids": [
"CSAFPID-0001",
"CSAFPID-0002"
]
},
{
"category": "mitigation",
"details": "AS 4.7.3 (Planned release date: 2020-04-10) and higher",
"product_ids": [
"CSAFPID-0001",
"CSAFPID-0002"
]
},
{
"category": "mitigation",
"details": "AS 4.8.2 (Planned release date: 2020-06-11) and higher",
"product_ids": [
"CSAFPID-0001",
"CSAFPID-0002"
]
},
{
"category": "mitigation",
"details": "B\u0026R reports the above-mentioned dates denoted as planned are preliminary and may be subject to change. Registered users may approach their local B\u0026R service organization in case of questions. B\u0026R recommends that affected users evaluate their need for the SNMP service and disable it if possible. For more information related to this vulnerability please refer to the B\u0026R advisory. For additional information and support, please contact B\u0026R service.",
"product_ids": [
"CSAFPID-0001",
"CSAFPID-0002"
],
"url": "https://www.br-automation.com/en-us/service/cyber-security/"
}
],
"scores": [
{
"cvss_v3": {
"baseScore": 9.4,
"baseSeverity": "CRITICAL",
"vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H",
"version": "3.0"
},
"products": [
"CSAFPID-0001",
"CSAFPID-0002"
]
}
],
"title": "CVE-2019-19108"
}
]
}
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.