Siemens BFCClient OpenSSL vulnerabilities affect encryption
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Five OpenSSL vulnerabilities in Siemens BFCClient prior to v2.17 enable memory disclosure, denial of service, or altered behavior via crafted certificates or encrypted data.
Siemens BFCClient versions prior to 2.17 contain five OpenSSL-related vulnerabilities that can be exploited remotely with low attack complexity. The vulnerabilities stem from underlying OpenSSL flaws affecting cryptographic operations and certificate processing. A buffer overflow in SM2 decryption (CVE-2021-3711) can overflow heap buffers by up to 62 bytes when processing specially crafted encrypted data, potentially altering application behavior or causing crashes. An out-of-bounds read in ASN.1 string handling (CVE-2021-3712) can leak private memory contents including private keys or crash the application. An infinite loop vulnerability in modular square root computation (CVE-2022-0778) affects certificate parsing and can be triggered by malformed elliptic curve parameters, causing denial of service. A type confusion vulnerability in X.400 address processing (CVE-2023-0286) during CRL checking can allow memory disclosure or denial of service. An improper certificate validation flaw (CVE-2023-0464) in policy constraint processing can trigger exponential computational use, enabling DoS attacks.
CISA reports no known public exploitation of these specific vulnerabilities at the time of advisory publication. The primary mitigation is updating BFCClient to version 2.17 or later. As an interim measure for CVE-2023-0286, organizations can disable CRL checking if operationally feasible. General ICS hardening measures including network segmentation, firewall protection, and VPN use for remote access are recommended.
Mentioned in this report
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-21
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,853 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs