CVE-2022-30317

{
  "id": "CVE-2022-30317",
  "cveTags": [],
  "metrics": {
    "cvssMetricV31": [
      {
        "type": "Primary",
        "source": "nvd@nist.gov",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 9.1,
          "attackVector": "NETWORK",
          "baseSeverity": "CRITICAL",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "NONE"
        },
        "impactScore": 5.2,
        "exploitabilityScore": 3.9
      }
    ]
  },
  "affected": [
    {
      "source": "cve@mitre.org",
      "affectedData": [
        {
          "vendor": "n/a",
          "product": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ]
    }
  ],
  "published": "2022-08-31T16:15:11.580",
  "references": [
    {
      "url": "https://www.cisa.gov/uscert/ics/advisories/icsa-22-242-07",
      "tags": [
        "Mitigation",
        "Third Party Advisory",
        "US Government Resource"
      ],
      "source": "cve@mitre.org"
    },
    {
      "url": "https://www.forescout.com/blog/",
      "tags": [
        "Not Applicable"
      ],
      "source": "cve@mitre.org"
    },
    {
      "url": "https://www.cisa.gov/uscert/ics/advisories/icsa-22-242-07",
      "tags": [
        "Mitigation",
        "Third Party Advisory",
        "US Government Resource"
      ],
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    },
    {
      "url": "https://www.forescout.com/blog/",
      "tags": [
        "Not Applicable"
      ],
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    }
  ],
  "vulnStatus": "Modified",
  "weaknesses": [
    {
      "type": "Primary",
      "source": "nvd@nist.gov",
      "description": [
        {
          "lang": "en",
          "value": "CWE-306"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "Honeywell Experion LX through 2022-05-06 has Missing Authentication for a Critical Function. According to FSCT-2022-0055, there is a Honeywell Experion LX Control Data Access (CDA) EpicMo protocol with unauthenticated functionality issue. The affected components are characterized as: Honeywell Control Data Access (CDA) EpicMo (55565/TCP). The potential impact is: Firmware manipulation, Denial of service. The Honeywell Experion LX Distributed Control System (DCS) utilizes the Control Data Access (CDA) EpicMo protocol (55565/TCP) for device diagnostics and maintenance purposes. This protocol does not have any authentication features, allowing any attacker capable of communicating with the ports in question to invoke (a subset of) desired functionality. There is no authentication functionality on the protocol in question. An attacker capable of invoking the protocols' functionalities could issue firmware download commands potentially allowing for firmware manipulation and reboot devices causing denial of service."
    },
    {
      "lang": "es",
      "value": "Honeywell Experion LX versiones hasta 06-05-2022, presenta una autenticación faltante para una función crítica. Según FSCT-2022-0055, se presenta un problema de acceso a datos de control (CDA) del protocolo EpicMo de Honeywell Experion LX con funcionalidad no autenticada. Los componentes afectados se caracterizan como: Honeywell Control Data Access (CDA) EpicMo (55565/TCP). El impacto potencial es: Manipulación del firmware, Denegación de servicio. El Sistema de Control Distribuido (DCS) Experion LX de Honeywell usa el protocolo de Acceso a Datos de Control (CDA) EpicMo (55565/TCP) para fines de diagnóstico y mantenimiento del dispositivo. Este protocolo no presenta ninguna función de autenticación, lo que permite a cualquier atacante capaz de comunicarse con los puertos en cuestión invocar (un subconjunto de) la funcionalidad deseada. El protocolo en cuestión no presenta ninguna funcionalidad de autenticación. Un atacante capaz de invocar las funcionalidades de los protocolos podría emitir comandos de descarga de firmware permitiendo potencialmente la manipulación del firmware y el reinicio de los dispositivos causando una denegación de servicio"
    }
  ],
  "lastModified": "2026-06-17T04:43:29.070",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:o:honeywell:experion_lx_firmware:*:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "2F50B4E5-8C60-4E80-BFCB-5B7F269F6571",
              "versionEndExcluding": "r520.1"
            }
          ],
          "operator": "OR"
        },
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:h:honeywell:experion_lx:-:*:*:*:*:*:*:*",
              "vulnerable": false,
              "matchCriteriaId": "3DDBD9EC-2D34-4A5F-B5B8-A15B36FDB5A4"
            }
          ],
          "operator": "OR"
        }
      ],
      "operator": "AND"
    }
  ],
  "sourceIdentifier": "cve@mitre.org"
}