CVE-2025-36539 (GCVE-0-2025-36539)

Vulnerability from cvelistv5 – Published: 2025-06-12 19:56 – Updated: 2025-06-12 20:04
VLAI?
Title
AVEVA PI Data Archive Uncaught Exception
Summary
AVEVA PI Data Archive products are vulnerable to an uncaught exception that, if exploited, could allow an authenticated user to shut down certain necessary PI Data Archive subsystems, resulting in a denial of service.
Severity ?
6.5 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
7.1 (High)
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CWE
Assigner
References
Impacted products
Vendor Product Version
AVEVA PI Data Archive Affected: 2023 , ≤ 2018 SP3 Patch 4 (custom)
Create a notification for this product.
    AVEVA PI Data Archive Affected: 2023 Patch 1
Create a notification for this product.
    AVEVA PI Server Affected: 2023 , ≤ 2018 SP3 Patch 6 (custom)
Create a notification for this product.
    AVEVA PI Server Affected: 2023 Patch 1 , ≤ 2018 SP3 Patch 6 (custom)
Create a notification for this product.
Credits
AVEVA reported these vulnerabilities to CISA.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2025-36539",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-06-12T20:04:09.170573Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-06-12T20:04:23.575Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "PI Data Archive",
          "vendor": "AVEVA",
          "versions": [
            {
              "lessThanOrEqual": "2018 SP3 Patch 4",
              "status": "affected",
              "version": "2023",
              "versionType": "custom"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "product": "PI Data Archive",
          "vendor": "AVEVA",
          "versions": [
            {
              "status": "affected",
              "version": "2023 Patch 1"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "product": "PI Server",
          "vendor": "AVEVA",
          "versions": [
            {
              "lessThanOrEqual": "2018 SP3 Patch 6",
              "status": "affected",
              "version": "2023",
              "versionType": "custom"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "product": "PI Server",
          "vendor": "AVEVA",
          "versions": [
            {
              "lessThanOrEqual": "2018 SP3 Patch 6",
              "status": "affected",
              "version": "2023 Patch 1",
              "versionType": "custom"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "AVEVA reported these vulnerabilities to CISA."
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "AVEVA PI Data Archive products \nare vulnerable to an uncaught exception that, if exploited, could allow \nan authenticated user to shut down certain necessary PI Data Archive \nsubsystems, resulting in a denial of service."
            }
          ],
          "value": "AVEVA PI Data Archive products \nare vulnerable to an uncaught exception that, if exploited, could allow \nan authenticated user to shut down certain necessary PI Data Archive \nsubsystems, resulting in a denial of service."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 6.5,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "integrityImpact": "NONE",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 7.1,
            "baseSeverity": "HIGH",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "HIGH",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-248",
              "description": "CWE-248",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-06-12T19:56:33.320Z",
        "orgId": "7d14cffa-0d7d-4270-9dc0-52cabd5a23a6",
        "shortName": "icscert"
      },
      "references": [
        {
          "url": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-162-07"
        },
        {
          "url": "https://www.aveva.com/en/support-and-success/cyber-security-updates/"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eAVEVA recommends that organizations evaluate the impact of these \nvulnerabilities based on their operational environment, architecture, \nand product implementation. Users with affected product versions should \napply security updates to mitigate the risk of exploit.\u003c/p\u003e\u003cp\u003eAll affected versions of PI Data \nArchive and PI Server can be fixed by upgrading to PI Server 2024 or \nhigher. From \u003ca target=\"_blank\" rel=\"nofollow\" href=\"https://my.osisoft.com/\"\u003eOSISoft Customer Portal\u003c/a\u003e, search for \"AVEVA PI Server\" and select version 2024 or higher.\u003c/p\u003e\u003cp\u003eFor additional information please refer to \u003ca target=\"_blank\" rel=\"nofollow\" href=\"https://www.aveva.com/en/support-and-success/cyber-security-updates/\"\u003eAVEVA-2025-001\u003c/a\u003e.\n\n\u003cbr\u003e\u003c/p\u003e"
            }
          ],
          "value": "AVEVA recommends that organizations evaluate the impact of these \nvulnerabilities based on their operational environment, architecture, \nand product implementation. Users with affected product versions should \napply security updates to mitigate the risk of exploit.\n\nAll affected versions of PI Data \nArchive and PI Server can be fixed by upgrading to PI Server 2024 or \nhigher. From  OSISoft Customer Portal https://my.osisoft.com/ , search for \"AVEVA PI Server\" and select version 2024 or higher.\n\nFor additional information please refer to  AVEVA-2025-001 https://www.aveva.com/en/support-and-success/cyber-security-updates/ ."
        }
      ],
      "source": {
        "advisory": "ICSA-25-162-07",
        "discovery": "INTERNAL"
      },
      "title": "AVEVA PI Data Archive Uncaught Exception",
      "workarounds": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eAVEVA recommends that organizations evaluate the impact of these \nvulnerabilities based on their operational environment, architecture, \nand product implementation. Users with affected product versions should \napply security updates to mitigate the risk of exploit.\u003c/p\u003e\u003cp\u003eAVEVA further recommends users follow general defensive measures:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eMonitor liveness of PI Network Manager and PI Archive Subsystem services.\u003c/li\u003e\n\u003cli\u003eSet the PI Network Manager and PI Archive Subsystem services to automatically restart.\u003c/li\u003e\n\u003cli\u003eLimit Port 5450 access to trusted workstations and software.\u003c/li\u003e\n\u003cli\u003eFor a list of PI System firewall port requirements, see knowledge base article \u003ca target=\"_blank\" rel=\"nofollow\" href=\"https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=KB01162\"\u003eKB01162 - Firewall Port Requirements\u003c/a\u003e.\u003c/li\u003e\u003c/ul\u003e\u003cli\u003eImpact and severity of vulnerabilities can be reduced through \nindustry accepted IT practices. Please consult your IT engineer for \nadvice on how to best implement these firewall restrictions in your \norganization\u0027s architecture. OSIsoft technical support provides guidance\n on architectural approaches, backup procedures, network defenses, and \noperating system configuration.\u003c/li\u003e\u003cli\u003eFor a starting point on PI System security best practices, see knowledge base article \u003ca target=\"_blank\" rel=\"nofollow\" href=\"https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=KB00833\"\u003eKB00833 - Seven best practices for securing your PI Server\u003c/a\u003e.\u003c/li\u003e\u003cp\u003eFor additional information please refer to \u003ca target=\"_blank\" rel=\"nofollow\" href=\"https://www.aveva.com/en/support-and-success/cyber-security-updates/\"\u003eAVEVA-2025-001\u003c/a\u003e.\n\n\u003cbr\u003e\u003c/p\u003e"
            }
          ],
          "value": "AVEVA recommends that organizations evaluate the impact of these \nvulnerabilities based on their operational environment, architecture, \nand product implementation. Users with affected product versions should \napply security updates to mitigate the risk of exploit.\n\nAVEVA further recommends users follow general defensive measures:\n\n\n\n  *  Monitor liveness of PI Network Manager and PI Archive Subsystem services.\n\n  *  Set the PI Network Manager and PI Archive Subsystem services to automatically restart.\n\n  *  Limit Port 5450 access to trusted workstations and software.\n\n  *  For a list of PI System firewall port requirements, see knowledge base article  KB01162 - Firewall Port Requirements https://customers.osisoft.com/s/knowledgearticle .\n\n\n  *  Impact and severity of vulnerabilities can be reduced through \nindustry accepted IT practices. Please consult your IT engineer for \nadvice on how to best implement these firewall restrictions in your \norganization\u0027s architecture. OSIsoft technical support provides guidance\n on architectural approaches, backup procedures, network defenses, and \noperating system configuration.\n  *  For a starting point on PI System security best practices, see knowledge base article  KB00833 - Seven best practices for securing your PI Server https://customers.osisoft.com/s/knowledgearticle .\nFor additional information please refer to  AVEVA-2025-001 https://www.aveva.com/en/support-and-success/cyber-security-updates/ ."
        }
      ],
      "x_generator": {
        "engine": "Vulnogram 0.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "7d14cffa-0d7d-4270-9dc0-52cabd5a23a6",
    "assignerShortName": "icscert",
    "cveId": "CVE-2025-36539",
    "datePublished": "2025-06-12T19:56:33.320Z",
    "dateReserved": "2025-04-21T19:39:54.984Z",
    "dateUpdated": "2025-06-12T20:04:23.575Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-36539\",\"sourceIdentifier\":\"ics-cert@hq.dhs.gov\",\"published\":\"2025-06-12T20:15:21.250\",\"lastModified\":\"2025-06-16T12:32:18.840\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"AVEVA PI Data Archive products \\nare vulnerable to an uncaught exception that, if exploited, could allow \\nan authenticated user to shut down certain necessary PI Data Archive \\nsubsystems, resulting in a denial of service.\"},{\"lang\":\"es\",\"value\":\"Los productos AVEVA PI Data Archive son vulnerables a una excepci\u00f3n no detectada que, si se explota, podr\u00eda permitir que un usuario autenticado apague ciertos subsistemas necesarios de PI Data Archive, lo que resultar\u00eda en una denegaci\u00f3n de servicio.\"}],\"metrics\":{\"cvssMetricV40\":[{\"source\":\"ics-cert@hq.dhs.gov\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"4.0\",\"vectorString\":\"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X\",\"baseScore\":7.1,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"attackRequirements\":\"NONE\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"vulnConfidentialityImpact\":\"NONE\",\"vulnIntegrityImpact\":\"NONE\",\"vulnAvailabilityImpact\":\"HIGH\",\"subConfidentialityImpact\":\"NONE\",\"subIntegrityImpact\":\"NONE\",\"subAvailabilityImpact\":\"NONE\",\"exploitMaturity\":\"NOT_DEFINED\",\"confidentialityRequirement\":\"NOT_DEFINED\",\"integrityRequirement\":\"NOT_DEFINED\",\"availabilityRequirement\":\"NOT_DEFINED\",\"modifiedAttackVector\":\"NOT_DEFINED\",\"modifiedAttackComplexity\":\"NOT_DEFINED\",\"modifiedAttackRequirements\":\"NOT_DEFINED\",\"modifiedPrivilegesRequired\":\"NOT_DEFINED\",\"modifiedUserInteraction\":\"NOT_DEFINED\",\"modifiedVulnConfidentialityImpact\":\"NOT_DEFINED\",\"modifiedVulnIntegrityImpact\":\"NOT_DEFINED\",\"modifiedVulnAvailabilityImpact\":\"NOT_DEFINED\",\"modifiedSubConfidentialityImpact\":\"NOT_DEFINED\",\"modifiedSubIntegrityImpact\":\"NOT_DEFINED\",\"modifiedSubAvailabilityImpact\":\"NOT_DEFINED\",\"Safety\":\"NOT_DEFINED\",\"Automatable\":\"NOT_DEFINED\",\"Recovery\":\"NOT_DEFINED\",\"valueDensity\":\"NOT_DEFINED\",\"vulnerabilityResponseEffort\":\"NOT_DEFINED\",\"providerUrgency\":\"NOT_DEFINED\"}}],\"cvssMetricV31\":[{\"source\":\"ics-cert@hq.dhs.gov\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":6.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":2.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"ics-cert@hq.dhs.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-248\"}]}],\"references\":[{\"url\":\"https://www.aveva.com/en/support-and-success/cyber-security-updates/\",\"source\":\"ics-cert@hq.dhs.gov\"},{\"url\":\"https://www.cisa.gov/news-events/ics-advisories/icsa-25-162-07\",\"source\":\"ics-cert@hq.dhs.gov\"}]}}",
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2025-36539\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2025-06-12T20:04:09.170573Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2025-06-12T20:04:14.620Z\"}}], \"cna\": {\"title\": \"AVEVA PI Data Archive Uncaught Exception\", \"source\": {\"advisory\": \"ICSA-25-162-07\", \"discovery\": \"INTERNAL\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"finder\", \"value\": \"AVEVA reported these vulnerabilities to CISA.\"}], \"metrics\": [{\"format\": \"CVSS\", \"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 6.5, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"NONE\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}, {\"format\": \"CVSS\", \"cvssV4_0\": {\"Safety\": \"NOT_DEFINED\", \"version\": \"4.0\", \"Recovery\": \"NOT_DEFINED\", \"baseScore\": 7.1, \"Automatable\": \"NOT_DEFINED\", \"attackVector\": \"NETWORK\", \"baseSeverity\": \"HIGH\", \"valueDensity\": \"NOT_DEFINED\", \"vectorString\": \"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N\", \"providerUrgency\": \"NOT_DEFINED\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"attackRequirements\": \"NONE\", \"privilegesRequired\": \"LOW\", \"subIntegrityImpact\": \"NONE\", \"vulnIntegrityImpact\": \"NONE\", \"subAvailabilityImpact\": \"NONE\", \"vulnAvailabilityImpact\": \"HIGH\", \"subConfidentialityImpact\": \"NONE\", \"vulnConfidentialityImpact\": \"NONE\", \"vulnerabilityResponseEffort\": \"NOT_DEFINED\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"vendor\": \"AVEVA\", \"product\": \"PI Data Archive\", \"versions\": [{\"status\": \"affected\", \"version\": \"2023\", \"versionType\": \"custom\", \"lessThanOrEqual\": \"2018 SP3 Patch 4\"}], \"defaultStatus\": \"unaffected\"}, {\"vendor\": \"AVEVA\", \"product\": \"PI Data Archive\", \"versions\": [{\"status\": \"affected\", \"version\": \"2023 Patch 1\"}], \"defaultStatus\": \"unaffected\"}, {\"vendor\": \"AVEVA\", \"product\": \"PI Server\", \"versions\": [{\"status\": \"affected\", \"version\": \"2023\", \"versionType\": \"custom\", \"lessThanOrEqual\": \"2018 SP3 Patch 6\"}], \"defaultStatus\": \"unaffected\"}, {\"vendor\": \"AVEVA\", \"product\": \"PI Server\", \"versions\": [{\"status\": \"affected\", \"version\": \"2023 Patch 1\", \"versionType\": \"custom\", \"lessThanOrEqual\": \"2018 SP3 Patch 6\"}], \"defaultStatus\": \"unaffected\"}], \"solutions\": [{\"lang\": \"en\", \"value\": \"AVEVA recommends that organizations evaluate the impact of these \\nvulnerabilities based on their operational environment, architecture, \\nand product implementation. Users with affected product versions should \\napply security updates to mitigate the risk of exploit.\\n\\nAll affected versions of PI Data \\nArchive and PI Server can be fixed by upgrading to PI Server 2024 or \\nhigher. From  OSISoft Customer Portal https://my.osisoft.com/ , search for \\\"AVEVA PI Server\\\" and select version 2024 or higher.\\n\\nFor additional information please refer to  AVEVA-2025-001 https://www.aveva.com/en/support-and-success/cyber-security-updates/ .\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eAVEVA recommends that organizations evaluate the impact of these \\nvulnerabilities based on their operational environment, architecture, \\nand product implementation. Users with affected product versions should \\napply security updates to mitigate the risk of exploit.\u003c/p\u003e\u003cp\u003eAll affected versions of PI Data \\nArchive and PI Server can be fixed by upgrading to PI Server 2024 or \\nhigher. From \u003ca target=\\\"_blank\\\" rel=\\\"nofollow\\\" href=\\\"https://my.osisoft.com/\\\"\u003eOSISoft Customer Portal\u003c/a\u003e, search for \\\"AVEVA PI Server\\\" and select version 2024 or higher.\u003c/p\u003e\u003cp\u003eFor additional information please refer to \u003ca target=\\\"_blank\\\" rel=\\\"nofollow\\\" href=\\\"https://www.aveva.com/en/support-and-success/cyber-security-updates/\\\"\u003eAVEVA-2025-001\u003c/a\u003e.\\n\\n\u003cbr\u003e\u003c/p\u003e\", \"base64\": false}]}], \"references\": [{\"url\": \"https://www.cisa.gov/news-events/ics-advisories/icsa-25-162-07\"}, {\"url\": \"https://www.aveva.com/en/support-and-success/cyber-security-updates/\"}], \"workarounds\": [{\"lang\": \"en\", \"value\": \"AVEVA recommends that organizations evaluate the impact of these \\nvulnerabilities based on their operational environment, architecture, \\nand product implementation. Users with affected product versions should \\napply security updates to mitigate the risk of exploit.\\n\\nAVEVA further recommends users follow general defensive measures:\\n\\n\\n\\n  *  Monitor liveness of PI Network Manager and PI Archive Subsystem services.\\n\\n  *  Set the PI Network Manager and PI Archive Subsystem services to automatically restart.\\n\\n  *  Limit Port 5450 access to trusted workstations and software.\\n\\n  *  For a list of PI System firewall port requirements, see knowledge base article  KB01162 - Firewall Port Requirements https://customers.osisoft.com/s/knowledgearticle .\\n\\n\\n  *  Impact and severity of vulnerabilities can be reduced through \\nindustry accepted IT practices. Please consult your IT engineer for \\nadvice on how to best implement these firewall restrictions in your \\norganization\u0027s architecture. OSIsoft technical support provides guidance\\n on architectural approaches, backup procedures, network defenses, and \\noperating system configuration.\\n  *  For a starting point on PI System security best practices, see knowledge base article  KB00833 - Seven best practices for securing your PI Server https://customers.osisoft.com/s/knowledgearticle .\\nFor additional information please refer to  AVEVA-2025-001 https://www.aveva.com/en/support-and-success/cyber-security-updates/ .\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eAVEVA recommends that organizations evaluate the impact of these \\nvulnerabilities based on their operational environment, architecture, \\nand product implementation. Users with affected product versions should \\napply security updates to mitigate the risk of exploit.\u003c/p\u003e\u003cp\u003eAVEVA further recommends users follow general defensive measures:\u003c/p\u003e\\n\u003cul\u003e\\n\u003cli\u003eMonitor liveness of PI Network Manager and PI Archive Subsystem services.\u003c/li\u003e\\n\u003cli\u003eSet the PI Network Manager and PI Archive Subsystem services to automatically restart.\u003c/li\u003e\\n\u003cli\u003eLimit Port 5450 access to trusted workstations and software.\u003c/li\u003e\\n\u003cli\u003eFor a list of PI System firewall port requirements, see knowledge base article \u003ca target=\\\"_blank\\\" rel=\\\"nofollow\\\" href=\\\"https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=KB01162\\\"\u003eKB01162 - Firewall Port Requirements\u003c/a\u003e.\u003c/li\u003e\u003c/ul\u003e\u003cli\u003eImpact and severity of vulnerabilities can be reduced through \\nindustry accepted IT practices. Please consult your IT engineer for \\nadvice on how to best implement these firewall restrictions in your \\norganization\u0027s architecture. OSIsoft technical support provides guidance\\n on architectural approaches, backup procedures, network defenses, and \\noperating system configuration.\u003c/li\u003e\u003cli\u003eFor a starting point on PI System security best practices, see knowledge base article \u003ca target=\\\"_blank\\\" rel=\\\"nofollow\\\" href=\\\"https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=KB00833\\\"\u003eKB00833 - Seven best practices for securing your PI Server\u003c/a\u003e.\u003c/li\u003e\u003cp\u003eFor additional information please refer to \u003ca target=\\\"_blank\\\" rel=\\\"nofollow\\\" href=\\\"https://www.aveva.com/en/support-and-success/cyber-security-updates/\\\"\u003eAVEVA-2025-001\u003c/a\u003e.\\n\\n\u003cbr\u003e\u003c/p\u003e\", \"base64\": false}]}], \"x_generator\": {\"engine\": \"Vulnogram 0.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"AVEVA PI Data Archive products \\nare vulnerable to an uncaught exception that, if exploited, could allow \\nan authenticated user to shut down certain necessary PI Data Archive \\nsubsystems, resulting in a denial of service.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"AVEVA PI Data Archive products \\nare vulnerable to an uncaught exception that, if exploited, could allow \\nan authenticated user to shut down certain necessary PI Data Archive \\nsubsystems, resulting in a denial of service.\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-248\", \"description\": \"CWE-248\"}]}], \"providerMetadata\": {\"orgId\": \"7d14cffa-0d7d-4270-9dc0-52cabd5a23a6\", \"shortName\": \"icscert\", \"dateUpdated\": \"2025-06-12T19:56:33.320Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2025-36539\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2025-06-12T20:04:23.575Z\", \"dateReserved\": \"2025-04-21T19:39:54.984Z\", \"assignerOrgId\": \"7d14cffa-0d7d-4270-9dc0-52cabd5a23a6\", \"datePublished\": \"2025-06-12T19:56:33.320Z\", \"assignerShortName\": \"icscert\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.1"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.



Detection rules are retrieved from Rulezet.