2NGA002813

Vulnerability from csaf_abb - Published: 2025-11-03 00:30 - Updated: 2025-11-03 00:30
Summary
PCM600 SharpZip library vulnerability

Notes

Summary
An update is available that resolves vulnerability in the product versions listed as affected in this advisory. An attacker who successfully exploited this vulnerability could insert and run arbitrary code in the system.
General security recommendations
For any installation of software-related ABB 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.
Support
For additional instructions and support please contact your local ABB service organization. For contact information, see www.abb.com/contactcenters. 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 ABB. ABB 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 ABB 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 ABB 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 ABB, 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.
Mitigating factors
Mitigating factors describe conditions and circumstances that make an attack that exploits vulnerability difficult or less likely to succeed. Refer to section “General security recommendations” for further advise on how to keep your system secure.
Purpose
ABB 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, ABB 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 ABB 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 ABB’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
What causes this vulnerability? The vulnerability is caused by SharpZipLib allowing attackers to write to arbitrary files via a ../ (dot dot slash) in a Zip archive entry that is mishandled during extraction (i.e., changing the intended destination directory). This vulnerability is also known as 'Zip-Slip'. What is SharpZipLib? SharpZipLib is a compression/extraction library. It provides support for various compression and archive formats extraction. What might an attacker use the vulnerability to do? An attacker who successfully exploited this vulnerability could insert and run arbitrary code in a directory higher in the hierarchy than the destination extraction folder. How could an attacker exploit vulnerability? An attacker could try to exploit this vulnerability by creating a specially crafted compressed file and extracting the file to an affected system node. This would require that the attacker has local authenticated access to the system. Could this vulnerability be exploited remotely? No, to exploit this vulnerability an attacker would need to have local access to the affected system node. Can functional safety be affected by an exploit of this vulnerability? Yes. If successfully exploited, functional safety could be compromised if e.g., a configuration modified by an attacker is imported into a device performing safety-critical operations, such as a protection relay. What does the update do? The update eliminates this vulnerability by removing the affected component. When this security advisory was issued, had this vulnerability been publicly disclosed? Yes, this vulnerability has been publicly disclosed. When this security advisory was issued, had ABB received any reports that this vulnerability was being exploited? No, ABB had not received any information indicating that this vulnerability had been exploited when this security advisory was originally issued.

{
  "document": {
    "category": "csaf_security_advisory",
    "csaf_version": "2.0",
    "distribution": {
      "text": "\u00a9 Copyright 2025 ABB. All rights reserved.",
      "tlp": {
        "label": "WHITE"
      }
    },
    "lang": "en",
    "notes": [
      {
        "category": "summary",
        "text": "An update is available that resolves vulnerability in the product versions listed as affected in this advisory.\n\nAn attacker who successfully exploited this vulnerability could insert and run arbitrary code in the system.",
        "title": "Summary"
      },
      {
        "category": "other",
        "text": "For any installation of software-related ABB products we strongly recommend the following (non-exhaustive) list of cyber security practices:\n\n\u2013 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\n\u2013 Install physical controls so no unauthorized personnel can access your devices, components, peripheral equipment, and networks.\n\n\u2013 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\n\u2013 Scan all data imported into your environment before use to detect potential malware infections.\n\n\u2013 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\n\u2013 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\n\u2013 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",
        "title": "General security recommendations"
      },
      {
        "category": "other",
        "text": "For additional instructions and support please contact your local ABB service organization. For contact information, see www.abb.com/contactcenters.\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 ABB.\n\nABB 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 ABB 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 ABB 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 ABB, 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": "general",
        "text": "Mitigating factors describe conditions and circumstances that make an attack that exploits vulnerability difficult or less likely to succeed. \n\nRefer to section \u201cGeneral security recommendations\u201d for further advise on how to keep your system secure.\n",
        "title": "Mitigating factors"
      },
      {
        "category": "other",
        "text": "ABB 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, ABB 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 ABB 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 ABB\u2019s 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": "What causes this vulnerability?\n\nThe vulnerability is caused by SharpZipLib allowing attackers to write to arbitrary files via a ../ (dot dot slash) in a Zip archive entry that is mishandled during extraction (i.e., changing the intended destination directory). This vulnerability is also known as \u0027Zip-Slip\u0027.\n\nWhat is SharpZipLib?\n\nSharpZipLib is a compression/extraction library. It provides support for various compression and archive formats extraction.\n\nWhat might an attacker use the vulnerability to do?\n\nAn attacker who successfully exploited this vulnerability could insert and run arbitrary code in a directory higher in the hierarchy than the destination extraction folder.\n\nHow could an attacker exploit vulnerability?\n\nAn attacker could try to exploit this vulnerability by creating a specially crafted compressed file and extracting the file to an affected system node. This would require that the attacker has local authenticated access to the system.\n\nCould this vulnerability be exploited remotely? \n\nNo, to exploit this vulnerability an attacker would need to have local access to the affected system node.\n\nCan functional safety be affected by an exploit of this vulnerability?\n\nYes. If successfully exploited, functional safety could be compromised if e.g., a configuration modified by an attacker is imported into a device performing safety-critical operations, such as a protection relay.\n\nWhat does the update do?\n\nThe update eliminates this vulnerability by removing the affected component.\n\nWhen this security advisory was issued, had this vulnerability been publicly disclosed?\n\nYes, this vulnerability has been publicly disclosed.\n\nWhen this security advisory was issued, had ABB received any reports that this vulnerability was being exploited?\n\nNo, ABB had not received any information indicating that this vulnerability had been exploited when this security advisory was originally issued.",
        "title": "Frequently Asked Questions"
      }
    ],
    "publisher": {
      "category": "vendor",
      "name": "ABB PSIRT",
      "namespace": "https://global.abb/group/en/technology/cyber-security/alerts-and-notifications"
    },
    "references": [
      {
        "category": "self",
        "summary": "ABB CYBERSECURITY ADVISORY - PDF version ",
        "url": "https://search.abb.com/library/Download.aspx?DocumentID=2NGA002813\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
      },
      {
        "category": "self",
        "summary": "ABB CYBERSECURITY ADVISORY - CSAF version ",
        "url": "https://psirt.abb.com/csaf/2025/2nga002813.json"
      },
      {
        "summary": "1MRS758440, Rev. H PCM600 Cyber Security Deployment Guideline\n",
        "url": "https://search.abb.com/library/Download.aspx?DocumentID=1MRS758440\u0026LanguageCode=en\u0026DocumentPartId=ABB\u0026Action=Launch"
      }
    ],
    "title": "PCM600 SharpZip library vulnerability",
    "tracking": {
      "current_release_date": "2025-11-03T00:30:00.000Z",
      "generator": {
        "date": "2025-10-28T13:19:51.592Z",
        "engine": {
          "name": "Secvisogram",
          "version": "2.5.38"
        }
      },
      "id": "2NGA002813",
      "initial_release_date": "2025-11-03T00:30:00.000Z",
      "revision_history": [
        {
          "date": "2025-11-03T00:30:00.000Z",
          "legacy_version": "A",
          "number": "1",
          "summary": "Initial version."
        }
      ],
      "status": "final",
      "version": "1"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "branches": [
                  {
                    "category": "product_version_range",
                    "name": "\u003e=1.5|\u003c=2.13",
                    "product": {
                      "name": "ABB Protection and Control IED manager PCM600 \u003e=1.5|\u003c=2.13",
                      "product_id": "AV1"
                    }
                  },
                  {
                    "category": "product_version",
                    "name": "2.14",
                    "product": {
                      "name": "ABB Protection and Control IED manager PCM600 2.14",
                      "product_id": "FX1"
                    }
                  }
                ],
                "category": "product_name",
                "name": "PCM600"
              }
            ],
            "category": "product_family",
            "name": "Protection and Control IED manager"
          }
        ],
        "category": "vendor",
        "name": "ABB"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2018-1002208",
      "cwe": {
        "id": "CWE-22",
        "name": "Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027)"
      },
      "notes": [
        {
          "category": "description",
          "text": "A vulnerability exists in the SharpZip.dll included in the product versions listed above. An attacker could exploit vulnerability by providing a specially crafted message to the system node, causing insertion, and running of arbitrary code.",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "fixed": [
          "FX1"
        ],
        "known_affected": [
          "AV1"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "NVD - CVE-2018-1002208",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2018-1002208"
        }
      ],
      "remediations": [
        {
          "category": "vendor_fix",
          "details": "The problem is corrected in the following product version:\n\nABB Protection and control IED manager PCM600 version 2.14.\n\nABB recommends that customers apply the update at earliest convenience.\n\nNote: RE_630 protection relays are not compatible with PCM600 version 2.14. When using earlier PCM600 versions with RE_630, the known vulnerability must be mitigated through system-level defenses. For mitigation guidance, refer to the General Security Recommendations.",
          "product_ids": [
            "AV1"
          ]
        }
      ],
      "scores": [
        {
          "cvss_v3": {
            "attackComplexity": "HIGH",
            "attackVector": "LOCAL",
            "availabilityImpact": "NONE",
            "baseScore": 4.4,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "environmentalScore": 4,
            "environmentalSeverity": "MEDIUM",
            "exploitCodeMaturity": "PROOF_OF_CONCEPT",
            "integrityImpact": "HIGH",
            "privilegesRequired": "LOW",
            "remediationLevel": "OFFICIAL_FIX",
            "reportConfidence": "CONFIRMED",
            "scope": "UNCHANGED",
            "temporalScore": 4,
            "temporalSeverity": "MEDIUM",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N/E:P/RL:O/RC:C",
            "version": "3.1"
          },
          "products": [
            "AV1"
          ]
        }
      ],
      "title": "CVE-2018-1002208"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…