SA26P003

Vulnerability from csaf_abb - Published: 2026-11-09 00:30 - Updated: 2026-11-09 00:30
Summary
OpenSSL Vulnerabilities in B&R products
Notes
Summary: B&R is aware of public reports of a vulnerability in the product versions listed as affected in the advisory. An attacker who successfully exploited this vulnerability could cause the product to stop or insert and run arbitrary code.
Support: For additional instructions and support please contact your local B&R service organization. For contact information, see https://www.br-automation.com/en/about-us/locations/. Information about ABB’s cyber security program and capabilities can be found at www.abb.com/cybersecurity.
Notice: The information in this document is subject to change without notice, and should not be construed as a commitment by B&R. B&R provides no warranty, express or implied, including warranties of merchantability and fitness for a particular purpose, for the information contained in this document, and assumes no responsibility for any errors that may appear in this document. In no event shall B&R or any of its suppliers be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, or from the use of any hardware or software described in this document, even if B&R or its suppliers have been advised of the possibility of such damages. This document and parts hereof must not be reproduced or copied without written permission from B&R, and the contents hereof must not be imparted to a third party nor used for any unauthorized purpose. All rights to registrations and trademarks reside with their respective owners.
General security recommendations: For any installation of software-related B&R products we strongly recommend the following (non-exhaustive) list of cyber security practices: - Isolate special purpose networks (e.g. for automation systems) and remote devices behind firewalls and separate them from any general-purpose network (e.g. office or home networks). - Install physical controls so no unauthorized personnel can access your devices, components, peripheral equipment, and networks. - Never connect programming software or computers containing programing software to any network other than the network for the devices that it is intended for. - Scan all data imported into your environment before use to detect potential malware infections. - Minimize network exposure for all applications and endpoints to ensure that they are not accessible from the Internet unless they are designed for such exposure and the intended use requires such. - Ensure all nodes are always up to date in terms of installed software, operating system, and firmware patches as well as anti-virus and firewall. - When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices. For more information on recommended practices, please refer to the following documents listed in the reference section: - Defense in Depth for B&R products
Purpose: B&R has a rigorous internal cyber security continuous improvement process which involves regular testing with industry leading tools and periodic assessments to identify potential product issues. Occasionally an issue is determined to be a design or coding flaw with implications that may impact product cyber security. When a potential product vulnerability is identified or reported, B&R immediately initiates our vulnerability handling process. This entails validating if the issue is in fact a product issue, identifying root causes, determining what related products may be impacted, developing a remediation, and notifying end users and governmental organizations. The resulting Cyber Security Advisory intends to notify customers of the vulnerability and provide details on which products are impacted, how to mitigate the vulnerability or explain workarounds that minimize the potential risk as much as possible. The release of a Cyber Security Advisory should not be misconstrued as an affirmation or indication of an active threat or ongoing campaign targeting the products mentioned here. If B&R is aware of any specific threats, it will be clearly mentioned in the communication. The publication of this Cyber Security Advisory is an example of B&R's commitment to the user community in support of this critical topic. Responsible disclosure is an important element in the chain of trust we work to maintain with our many customers. The release of an Advisory provides timely information which is essential to help ensure our customers are fully informed.
Frequently asked questions: Could the vulnerabilities be exploited remotely? - Yes, an attacker who has network access to an affected system node could exploit these vulnerabilities. Recommended practices include that process control systems are physically protected, have no direct connections to the Internet, and are separated from other networks by means of a firewall system that has a minimal number of ports exposed. What does the update do? - The update removes the vulnerabilities by applying a fixed OpenSSL version. When this security advisory was issued, had these vulnerabilities been publicly disclosed? - Yes, this vulnerability has been publicly disclosed. When this security advisory was issued, had B&R received any reports that these vulnerabilities were being exploited? - No, B&R had not received any information indicating that these vulnerabilities were exploited when this security advisory was originally issued.
CVE-2025-11187

PBMAC1 parameters in PKCS#12 files are missing validation which can trigger a stack-based buffer overflow, invalid pointer or NULL pointer dereference during MAC verification. Impact summary: The stack buffer overflow or NULL pointer dereference may cause a crash leading to Denial of Service for an application that parses untrusted PKCS#12 files. The buffer overflow may also potentially enable code execution depending on platform mitigations. When verifying a PKCS#12 file that uses PBMAC1 for the MAC, the PBKDF2 salt and keylength parameters from the file are used without validation. If the value of keylength exceeds the size of the fixed stack buffer used for the derived key (64 bytes), the key derivation will overflow the buffer. The overflow length is attacker-controlled. Also, if the salt parameter is not an OCTET STRING type this can lead to invalid or NULL pointer dereference. Exploiting this issue requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For this reason the issue was assessed as Moderate severity. The FIPS modules in 3.6, 3.5 and 3.4 are not affected by this issue, as PKCS#12 processing is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5 and 3.4 are vulnerable to this issue. OpenSSL 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue as they do not support PBMAC1 in PKCS#12.

6.1 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:H/RL:O
CWE-476 - NULL Pointer Dereference
Affected products
Product Identifier Version Remediation
B&R Industrial Automation GmbH mapp View 6.6.0
B&R Industrial Automation GmbH / mapp View
 6.6.0
B&R Industrial Automation GmbH B&R Live Utils 3.0.2
B&R Industrial Automation GmbH / B&R Live Utils
 3.0.2
B&R Industrial Automation GmbH B&R Linux 12 1.1.1
B&R Industrial Automation GmbH / B&R Linux 12
 1.1.1
B&R Industrial Automation GmbH PPC80 1.8.2
B&R Industrial Automation GmbH / PPC80
 1.8.2
B&R Industrial Automation GmbH PPT50 1.8.0
B&R Industrial Automation GmbH / PPT50
 1.8.0
B&R Industrial Automation GmbH PPC50 1.8.0
B&R Industrial Automation GmbH / PPC50
 1.8.0
B&R Industrial Automation GmbH PPT80 1.8.2
B&R Industrial Automation GmbH / PPT80
 1.8.2
B&R Industrial Automation GmbH PFT51 1.8.2
B&R Industrial Automation GmbH / PFT51
 1.8.2
B&R Industrial Automation GmbH PFT50 1.8.0
B&R Industrial Automation GmbH / PFT50
 1.8.0
B&R Industrial Automation GmbH PPT30 1.8.0
B&R Industrial Automation GmbH / PPT30
 1.8.0
B&R Industrial Automation GmbH Terminal OS 1.8.0
B&R Industrial Automation GmbH / Terminal OS
 1.8.0
B&R Industrial Automation GmbH ADI OPC UA Server 3.0.0
B&R Industrial Automation GmbH / ADI OPC UA Server
 3.0.0
Product Identifier Version Remediation
B&R Industrial Automation GmbH mapp View <6.6.0
B&R Industrial Automation GmbH / mapp View
 <6.6.0
Vendor Fix
Mitigation
B&R Industrial Automation GmbH B&R Live Utils <3.0.2
B&R Industrial Automation GmbH / B&R Live Utils
 <3.0.2
Vendor Fix
Mitigation
B&R Industrial Automation GmbH B&R Linux 12 <1.1.1
B&R Industrial Automation GmbH / B&R Linux 12
 <1.1.1
Vendor Fix
Mitigation
B&R Industrial Automation GmbH PPC80 <1.8.2
B&R Industrial Automation GmbH / PPC80
 <1.8.2
Vendor Fix
Mitigation
B&R Industrial Automation GmbH PPT50 <1.8.0
B&R Industrial Automation GmbH / PPT50
 <1.8.0
Vendor Fix
Mitigation
B&R Industrial Automation GmbH PPC50 <1.8.0
B&R Industrial Automation GmbH / PPC50
 <1.8.0
Vendor Fix
Mitigation
B&R Industrial Automation GmbH PPT80 <1.8.2
B&R Industrial Automation GmbH / PPT80
 <1.8.2
Vendor Fix
Mitigation
B&R Industrial Automation GmbH PFT51 <1.8.2
B&R Industrial Automation GmbH / PFT51
 <1.8.2
Vendor Fix
Mitigation
B&R Industrial Automation GmbH PFT50 <1.8.0
B&R Industrial Automation GmbH / PFT50
 <1.8.0
Vendor Fix
Mitigation
B&R Industrial Automation GmbH PPT30 <1.8.0
B&R Industrial Automation GmbH / PPT30
 <1.8.0
Vendor Fix
Mitigation
B&R Industrial Automation GmbH Terminal OS <1.8.0
B&R Industrial Automation GmbH / Terminal OS
 <1.8.0
Vendor Fix
Mitigation
B&R Industrial Automation GmbH PVI <6.9.0
B&R Industrial Automation GmbH / PVI
 <6.9.0
Vendor Fix
Mitigation
B&R Industrial Automation GmbH ADI OPC UA Server <3.0.0
B&R Industrial Automation GmbH / ADI OPC UA Server
 <3.0.0
Vendor Fix
Mitigation
Product Identifier Version Remediation
B&R Industrial Automation GmbH Automation Runtime
B&R Industrial Automation GmbH
 —
B&R Industrial Automation GmbH OPC UA C/S TP
B&R Industrial Automation GmbH
 —
CVE-2025-15467

Parsing CMS AuthEnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution. When parsing CMS AuthEnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack-based out-of-bounds write before any authentication or tag verification occurs. Applications and services that parse untrusted CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable. Because the overflow occurs prior to authentication, no valid key material is required to trigger it. While exploitability to remote code execution depends on platform and toolchain mitigations, the stack-based write primitive represents a severe risk. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue. OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.

9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/RL:O
CWE-787 - Out-of-bounds Write
Affected products
Fixed 12 products, the same list as for CVE-2025-11187
Known affected 13 products, the same list as for CVE-2025-11187
Known not affected 2 products, the same list as for CVE-2025-11187
References
To clipboard 

{
  "document": {
    "category": "csaf_security_advisory",
    "csaf_version": "2.0",
    "distribution": {
      "text": "\u00a9 Copyright 2026 ABB. All rights reserved.",
      "tlp": {
        "label": "WHITE"
      }
    },
    "lang": "en",
    "notes": [
      {
        "category": "summary",
        "text": "B\u0026R is aware of public reports of a vulnerability in the product versions listed as affected in the advisory.\n\nAn attacker who successfully exploited this vulnerability could cause the product to stop or insert and run arbitrary code.",
        "title": "Summary"
      },
      {
        "category": "other",
        "text": "For additional instructions and support please contact your local B\u0026R service organization. For contact information, see https://www.br-automation.com/en/about-us/locations/.\n\nInformation about ABB\u2019s cyber security program and capabilities can be found at www.abb.com/cybersecurity.",
        "title": "Support"
      },
      {
        "category": "legal_disclaimer",
        "text": "The information in this document is subject to change without notice, and should not be construed as a commitment by B\u0026R.\n\nB\u0026R provides no warranty, express or implied, including warranties of merchantability and fitness for a particular purpose, for the information contained in this document, and assumes no responsibility for any errors that may appear in this document. In no event shall B\u0026R or any of its suppliers be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, or from the use of any hardware or software described in this document, even if B\u0026R or its suppliers have been advised of the possibility of such damages.\n\nThis document and parts hereof must not be reproduced or copied without written permission from B\u0026R, and the contents hereof must not be imparted to a third party nor used for any unauthorized purpose.\n\nAll rights to registrations and trademarks reside with their respective owners.",
        "title": "Notice"
      },
      {
        "category": "other",
        "text": "For any installation of software-related B\u0026R products we strongly recommend the following (non-exhaustive) list of cyber security practices:\n\n- Isolate special purpose networks (e.g. for automation systems) and remote devices behind firewalls and separate them from any general-purpose network (e.g. office or home networks).\n- Install physical controls so no unauthorized personnel can access your devices, components, peripheral equipment, and networks.\n- Never connect programming software or computers containing programing software to any network other than the network for the devices that it is intended for.\n- Scan all data imported into your environment before use to detect potential malware infections.\n- Minimize network exposure for all applications and endpoints to ensure that they are not accessible from the Internet unless they are designed for such exposure and the intended use requires such.\n- Ensure all nodes are always up to date in terms of installed software, operating system, and firmware patches as well as anti-virus and firewall.\n- When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices.\n\nFor more information on recommended practices, please refer to the following documents listed in the reference section:\n\n- Defense in Depth for B\u0026R products",
        "title": "General security recommendations"
      },
      {
        "category": "other",
        "text": "B\u0026R has a rigorous internal cyber security continuous improvement process which involves regular testing with industry leading tools and periodic assessments to identify potential product issues. Occasionally an issue is determined to be a design or coding flaw with implications that may impact product cyber security.\n\nWhen a potential product vulnerability is identified or reported, B\u0026R immediately initiates our vulnerability handling process. This entails validating if the issue is in fact a product issue, identifying root causes, determining what related products may be impacted, developing a remediation, and notifying end users and governmental organizations.\n\nThe resulting Cyber Security Advisory intends to notify customers of the vulnerability and provide details on which products are impacted, how to mitigate the vulnerability or explain workarounds that minimize the potential risk as much as possible. The release of a Cyber Security Advisory should not be misconstrued as an affirmation or indication of an active threat or ongoing campaign targeting the products mentioned here. If B\u0026R is aware of any specific threats, it will be clearly mentioned in the communication.\n\nThe publication of this Cyber Security Advisory is an example of B\u0026R\u0027s commitment to the user community in support of this critical topic. Responsible disclosure is an important element in the chain of trust we work to maintain with our many customers. The release of an Advisory provides timely information which is essential to help ensure our customers are fully informed.",
        "title": "Purpose"
      },
      {
        "category": "faq",
        "text": "Could the vulnerabilities be exploited remotely?\n- Yes, an attacker who has network access to an affected system node could exploit these vulnerabilities. Recommended practices include that process control systems are physically protected, have no direct connections to the Internet, and are separated from other networks by means of a firewall system that has a minimal number of ports exposed.\n\nWhat does the update do?\n- The update removes the vulnerabilities by applying a fixed OpenSSL version.\n\nWhen this security advisory was issued, had these vulnerabilities been publicly disclosed?\n- Yes, this vulnerability has been publicly disclosed.\n\nWhen this security advisory was issued, had B\u0026R received any reports that these vulnerabilities were being exploited?\n- No, B\u0026R had not received any information indicating that these vulnerabilities were exploited when this security advisory was originally issued.",
        "title": "Frequently asked questions"
      }
    ],
    "publisher": {
      "category": "vendor",
      "name": "ABB PSIRT",
      "namespace": "https://www.abb.com/global/en/company/about/cybersecurity/alerts-and-notifications"
    },
    "references": [
      {
        "category": "self",
        "summary": "B\u0026R CYBERSECURITY ADVISORY - PDF Version ",
        "url": "https://br-cws-assets.de-fra-1.linodeobjects.com/SA26P003-8f937685.pdf"
      },
      {
        "summary": "B\u0026R CYBERSECURITY ADVISORY - CSAF Version ",
        "url": "https://psirt.abb.com/csaf/2026/sa26p003.json"
      },
      {
        "summary": "Defense in Depth for B\u0026R products ",
        "url": "https://www.br-automation.com/fileadmin/Cyber_Security_-_Defense_in_Depth_for_BR_Products-bdd37e82.pdf"
      }
    ],
    "title": "OpenSSL Vulnerabilities in B\u0026R products",
    "tracking": {
      "current_release_date": "2026-11-09T00:30:00.000Z",
      "generator": {
        "date": "2026-11-09T10:11:27.891Z",
        "engine": {
          "name": "Secvisogram",
          "version": "2.6.17"
        }
      },
      "id": "SA26P003",
      "initial_release_date": "2026-11-09T00:30:00.000Z",
      "revision_history": [
        {
          "date": "2026-11-09T00:30:00.000Z",
          "legacy_version": "1.0",
          "number": "1",
          "summary": "Initial version."
        }
      ],
      "status": "final",
      "version": "1"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c6.6.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH mapp View \u003c6.6.0",
                  "product_id": "AV1"
                }
              },
              {
                "category": "product_version",
                "name": "6.6.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH mapp View 6.6.0",
                  "product_id": "FX1"
                }
              }
            ],
            "category": "product_name",
            "name": "mapp View"
          },
          {
            "category": "product_name",
            "name": "Automation Runtime",
            "product": {
              "name": "B\u0026R Industrial Automation GmbH Automation Runtime",
              "product_id": "NA1"
            }
          },
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c3.0.2",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH B\u0026R Live Utils \u003c3.0.2",
                  "product_id": "AV2"
                }
              },
              {
                "category": "product_version",
                "name": "3.0.2",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH B\u0026R Live Utils 3.0.2",
                  "product_id": "FX2"
                }
              }
            ],
            "category": "product_name",
            "name": "B\u0026R Live Utils"
          },
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c1.1.1",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH B\u0026R Linux 12 \u003c1.1.1",
                  "product_id": "AV3"
                }
              },
              {
                "category": "product_version",
                "name": "1.1.1",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH B\u0026R Linux 12 1.1.1",
                  "product_id": "FX3"
                }
              }
            ],
            "category": "product_name",
            "name": "B\u0026R Linux 12"
          },
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c1.8.2",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PPC80 \u003c1.8.2",
                  "product_id": "AV4"
                }
              },
              {
                "category": "product_version",
                "name": "1.8.2",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PPC80 1.8.2",
                  "product_id": "FX4"
                }
              }
            ],
            "category": "product_name",
            "name": "PPC80"
          },
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c1.8.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PPT50 \u003c1.8.0",
                  "product_id": "AV5"
                }
              },
              {
                "category": "product_version",
                "name": "1.8.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PPT50 1.8.0",
                  "product_id": "FX5"
                }
              }
            ],
            "category": "product_name",
            "name": "PPT50"
          },
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c1.8.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PPC50 \u003c1.8.0",
                  "product_id": "AV6"
                }
              },
              {
                "category": "product_version",
                "name": "1.8.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PPC50 1.8.0",
                  "product_id": "FX6"
                }
              }
            ],
            "category": "product_name",
            "name": "PPC50"
          },
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c1.8.2",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PPT80 \u003c1.8.2",
                  "product_id": "AV7"
                }
              },
              {
                "category": "product_version",
                "name": "1.8.2",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PPT80 1.8.2",
                  "product_id": "FX7"
                }
              }
            ],
            "category": "product_name",
            "name": "PPT80"
          },
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c1.8.2",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PFT51 \u003c1.8.2",
                  "product_id": "AV8"
                }
              },
              {
                "category": "product_version",
                "name": "1.8.2",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PFT51 1.8.2",
                  "product_id": "FX8"
                }
              }
            ],
            "category": "product_name",
            "name": "PFT51"
          },
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c1.8.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PFT50 \u003c1.8.0",
                  "product_id": "AV9"
                }
              },
              {
                "category": "product_version",
                "name": "1.8.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PFT50 1.8.0",
                  "product_id": "FX9"
                }
              }
            ],
            "category": "product_name",
            "name": "PFT50"
          },
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c1.8.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PPT30 \u003c1.8.0",
                  "product_id": "AV10"
                }
              },
              {
                "category": "product_version",
                "name": "1.8.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PPT30 1.8.0",
                  "product_id": "FX10"
                }
              }
            ],
            "category": "product_name",
            "name": "PPT30"
          },
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c1.8.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH Terminal OS \u003c1.8.0",
                  "product_id": "AV11"
                }
              },
              {
                "category": "product_version",
                "name": "1.8.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH Terminal OS 1.8.0",
                  "product_id": "FX11"
                }
              }
            ],
            "category": "product_name",
            "name": "Terminal OS"
          },
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c6.9.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH PVI \u003c6.9.0",
                  "product_id": "AV12"
                }
              }
            ],
            "category": "product_name",
            "name": "PVI"
          },
          {
            "branches": [
              {
                "category": "product_version_range",
                "name": "\u003c3.0.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH ADI OPC UA Server \u003c3.0.0",
                  "product_id": "AV13"
                }
              },
              {
                "category": "product_version",
                "name": "3.0.0",
                "product": {
                  "name": "B\u0026R Industrial Automation GmbH ADI OPC UA Server 3.0.0",
                  "product_id": "FX12"
                }
              }
            ],
            "category": "product_name",
            "name": "ADI OPC UA Server"
          },
          {
            "category": "product_name",
            "name": "OPC UA C/S TP",
            "product": {
              "name": "B\u0026R Industrial Automation GmbH OPC UA C/S TP",
              "product_id": "NA2"
            }
          }
        ],
        "category": "vendor",
        "name": "B\u0026R Industrial Automation GmbH"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2025-11187",
      "cwe": {
        "id": "CWE-476",
        "name": "NULL Pointer Dereference"
      },
      "notes": [
        {
          "category": "description",
          "text": "PBMAC1 parameters in PKCS#12 files are missing validation which can trigger a stack-based buffer overflow, invalid pointer or NULL pointer dereference during MAC verification. Impact summary: The stack buffer overflow or NULL pointer dereference may cause a crash leading to Denial of Service for an application that parses untrusted PKCS#12 files. The buffer overflow may also potentially enable code execution depending on platform mitigations. When verifying a PKCS#12 file that uses PBMAC1 for the MAC, the PBKDF2 salt and keylength parameters from the file are used without validation. If the value of keylength exceeds the size of the fixed stack buffer used for the derived key (64 bytes), the key derivation will overflow the buffer. The overflow length is attacker-controlled. Also, if the salt parameter is not an OCTET STRING type this can lead to invalid or NULL pointer dereference. Exploiting this issue requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For this reason the issue was assessed as Moderate severity. The FIPS modules in 3.6, 3.5 and 3.4 are not affected by this issue, as PKCS#12 processing is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5 and 3.4 are vulnerable to this issue. OpenSSL 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue as they do not support PBMAC1 in PKCS#12.",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "fixed": [
          "FX1",
          "FX2",
          "FX3",
          "FX4",
          "FX5",
          "FX6",
          "FX7",
          "FX8",
          "FX9",
          "FX10",
          "FX11",
          "FX12"
        ],
        "known_affected": [
          "AV1",
          "AV2",
          "AV3",
          "AV4",
          "AV5",
          "AV6",
          "AV7",
          "AV8",
          "AV9",
          "AV10",
          "AV11",
          "AV12",
          "AV13"
        ],
        "known_not_affected": [
          "NA1",
          "NA2"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "NVD - CVE-2025-11187",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-11187"
        }
      ],
      "remediations": [
        {
          "category": "vendor_fix",
          "details": "The problem is corrected in the following product versions:\n\n- mapp View 6.6.0\n- B\u0026R Live Utils 3.0.2\n- B\u0026R Linux 12 1.1.1\n- PPC80 1.8.2\n- PPT50 1.8.0\n- PPC50 1.8.0\n- PPT80 1.8.2\n- PFT51 1.8.2\n- PFT50 1.8.0\n- PPT30 1.8.0\n- Terminal OS 1.8.0\n- ADI OPC UA Server 3.0.0\n\nB\u0026R recommends that impacted customers apply the update at earliest convenience.\n\nThe process to install updates is described in the user manual. The step to identify the installed product version is described in the user manual.",
          "product_ids": [
            "AV1",
            "AV2",
            "AV3",
            "AV4",
            "AV5",
            "AV6",
            "AV7",
            "AV8",
            "AV9",
            "AV10",
            "AV11",
            "AV13"
          ]
        },
        {
          "category": "vendor_fix",
          "details": "The problem is corrected in the following product version:\n\n- PVI 6.9.0 (pending)\n\nB\u0026R recommends that impacted customers apply the update at earliest convenience.\n\nThe process to install updates is described in the user manual. The step to identify the installed product version is described in the user manual.",
          "product_ids": [
            "AV12"
          ]
        },
        {
          "category": "mitigation",
          "details": "Customers are advised to review if their systems parse untrusted PKCS#12 files or CMS/PKCS#7 content, as standard TLS usage (e.g., HTTPS handshakes) typically does not trigger these issues.\n\nFor customers using OpenSSL solely for TLS (e.g., HTTPS or secure transport), exposure could be minimal since these vulnerabilities typically require processing specific certificate or signed data formats not involved in standard TLS handshakes.\n\nRefer to section \"General security recommendations\" for further advise on how to keep your system secure.",
          "product_ids": [
            "AV1",
            "AV2",
            "AV3",
            "AV4",
            "AV5",
            "AV6",
            "AV7",
            "AV8",
            "AV9",
            "AV10",
            "AV11",
            "AV12",
            "AV13"
          ]
        }
      ],
      "scores": [
        {
          "cvss_v3": {
            "attackComplexity": "LOW",
            "attackVector": "LOCAL",
            "availabilityImpact": "HIGH",
            "baseScore": 6.1,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "environmentalScore": 5.8,
            "environmentalSeverity": "MEDIUM",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "remediationLevel": "OFFICIAL_FIX",
            "scope": "UNCHANGED",
            "temporalScore": 5.8,
            "temporalSeverity": "MEDIUM",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:H/RL:O",
            "version": "3.1"
          },
          "products": [
            "AV1",
            "AV2",
            "AV3",
            "AV4",
            "AV5",
            "AV6",
            "AV7",
            "AV8",
            "AV9",
            "AV10",
            "AV11",
            "AV12",
            "AV13"
          ]
        }
      ],
      "title": "CVE-2025-11187"
    },
    {
      "cve": "CVE-2025-15467",
      "cwe": {
        "id": "CWE-787",
        "name": "Out-of-bounds Write"
      },
      "notes": [
        {
          "category": "description",
          "text": "Parsing CMS AuthEnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution. When parsing CMS AuthEnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack-based out-of-bounds write before any authentication or tag verification occurs. Applications and services that parse untrusted CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable. Because the overflow occurs prior to authentication, no valid key material is required to trigger it. While exploitability to remote code execution depends on platform and toolchain mitigations, the stack-based write primitive represents a severe risk. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue. OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "fixed": [
          "FX1",
          "FX2",
          "FX3",
          "FX4",
          "FX5",
          "FX6",
          "FX7",
          "FX8",
          "FX9",
          "FX10",
          "FX11",
          "FX12"
        ],
        "known_affected": [
          "AV1",
          "AV2",
          "AV3",
          "AV4",
          "AV5",
          "AV6",
          "AV7",
          "AV8",
          "AV9",
          "AV10",
          "AV11",
          "AV12",
          "AV13"
        ],
        "known_not_affected": [
          "NA1",
          "NA2"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "NVD - CVE-2025-15467",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-15467"
        }
      ],
      "remediations": [
        {
          "category": "vendor_fix",
          "details": "The problem is corrected in the following product versions:\n\n- mapp View 6.6.0\n- B\u0026R Live Utils 3.0.2\n- B\u0026R Linux 12 1.1.1\n- PPC80 1.8.2\n- PPT50 1.8.0\n- PPC50 1.8.0\n- PPT80 1.8.2\n- PFT51 1.8.2\n- PFT50 1.8.0\n- PPT30 1.8.0\n- Terminal OS 1.8.0\n- ADI OPC UA Server 3.0.0\n\nB\u0026R recommends that impacted customers apply the update at earliest convenience.\n\nThe process to install updates is described in the user manual. The step to identify the installed product version is described in the user manual.",
          "product_ids": [
            "AV1",
            "AV2",
            "AV3",
            "AV4",
            "AV5",
            "AV6",
            "AV7",
            "AV8",
            "AV9",
            "AV10",
            "AV11",
            "AV13"
          ]
        },
        {
          "category": "vendor_fix",
          "details": "The problem is corrected in the following product version:\n\n- PVI 6.9.0 (pending)\n\nB\u0026R recommends that impacted customers apply the update at earliest convenience.\n\nThe process to install updates is described in the user manual. The step to identify the installed product version is described in the user manual.",
          "product_ids": [
            "AV12"
          ]
        },
        {
          "category": "mitigation",
          "details": "Customers are advised to review if their systems parse untrusted PKCS#12 files or CMS/PKCS#7 content, as standard TLS usage (e.g., HTTPS handshakes) typically does not trigger these issues.\n\nFor customers using OpenSSL solely for TLS (e.g., HTTPS or secure transport), exposure could be minimal since these vulnerabilities typically require processing specific certificate or signed data formats not involved in standard TLS handshakes.\n\nRefer to section \"General security recommendations\" for further advise on how to keep your system secure.",
          "product_ids": [
            "AV1",
            "AV2",
            "AV3",
            "AV4",
            "AV5",
            "AV6",
            "AV7",
            "AV8",
            "AV9",
            "AV10",
            "AV11",
            "AV12",
            "AV13"
          ]
        }
      ],
      "scores": [
        {
          "cvss_v3": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "confidentialityImpact": "HIGH",
            "environmentalScore": 9.4,
            "environmentalSeverity": "CRITICAL",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "remediationLevel": "OFFICIAL_FIX",
            "scope": "UNCHANGED",
            "temporalScore": 9.4,
            "temporalSeverity": "CRITICAL",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/RL:O",
            "version": "3.1"
          },
          "products": [
            "AV1",
            "AV2",
            "AV3",
            "AV4",
            "AV5",
            "AV6",
            "AV7",
            "AV8",
            "AV9",
            "AV10",
            "AV11",
            "AV12",
            "AV13"
          ]
        }
      ],
      "title": "CVE-2025-15467"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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

JSON
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…




    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.