CVE-2022-30319

{
  "id": "CVE-2022-30319",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2022-30319",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2024-11-20T16:16:14.742165Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Primary",
        "source": "nvd@nist.gov",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 8.1,
          "attackVector": "ADJACENT_NETWORK",
          "baseSeverity": "HIGH",
          "vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "NONE",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 5.2,
        "exploitabilityScore": 2.8
      }
    ]
  },
  "affected": [
    {
      "source": "cve@mitre.org",
      "affectedData": [
        {
          "vendor": "n/a",
          "product": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ]
    }
  ],
  "published": "2022-07-28T16:15:11.500",
  "references": [
    {
      "url": "https://www.cisa.gov/uscert/ics/advisories/icsa-22-207-03",
      "tags": [
        "Third Party Advisory",
        "US Government Resource"
      ],
      "source": "cve@mitre.org"
    },
    {
      "url": "https://www.forescout.com/blog/",
      "tags": [
        "Third Party Advisory"
      ],
      "source": "cve@mitre.org"
    },
    {
      "url": "https://www.cisa.gov/uscert/ics/advisories/icsa-22-207-03",
      "tags": [
        "Third Party Advisory",
        "US Government Resource"
      ],
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    },
    {
      "url": "https://www.forescout.com/blog/",
      "tags": [
        "Third Party Advisory"
      ],
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    }
  ],
  "vulnStatus": "Modified",
  "weaknesses": [
    {
      "type": "Primary",
      "source": "nvd@nist.gov",
      "description": [
        {
          "lang": "en",
          "value": "CWE-290"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "Saia Burgess Controls (SBC) PCD through 2022-05-06 allows Authentication bypass. According to FSCT-2022-0062, there is a Saia Burgess Controls (SBC) PCD S-Bus authentication bypass issue. The affected components are characterized as: S-Bus (5050/UDP) authentication. The potential impact is: Authentication bypass. The Saia Burgess Controls (SBC) PCD controllers utilize the S-Bus protocol (5050/UDP) for a variety of engineering purposes. It is possible to configure a password in order to restrict access to sensitive engineering functionality. Authentication functions on the basis of a MAC/IP whitelist with inactivity timeout to which an authenticated client's MAC/IP is stored. UDP traffic can be spoofed to bypass the whitelist-based access control. Since UDP is stateless, an attacker capable of passively observing traffic can spoof arbitrary messages using the MAC/IP of an authenticated client. This allows the attacker access to sensitive engineering functionality such as uploading/downloading control logic and manipulating controller configuration."
    },
    {
      "lang": "es",
      "value": "Saia Burgess Controls (SBC) PCD versiones hasta 06-05-2022, permite una omisión de la Autenticación. De acuerdo con FSCT-2022-0062, se presenta un problema de omisión de autenticación S-Bus de Saia Burgess Controls (SBC) PCD. Los componentes afectados son caracterizados como: Autenticación S-Bus (5050/UDP). El impacto potencial es: Omisión de Autenticación. Los controladores PCD de Saia Burgess Controls (SBC) usan el protocolo S-Bus (5050/UDP) para diversos fines de ingeniería. Es posible configurar una contraseña para restringir el acceso a la funcionalidad de ingeniería confidencial. La autenticación funciona sobre la base de una lista blanca de MAC/IP con tiempo de inactividad en la que es almacenada la MAC/IP de un cliente autenticado. El tráfico UDP puede ser falsificado para omitir el control de acceso basado en la lista blanca. Como el UDP no presenta estado, un atacante capaz de observar pasivamente el tráfico puede falsificar mensajes arbitrarios usando la MAC/IP de un cliente autenticado. Esto permite al atacante acceder a funciones de ingeniería confidenciales, como la carga/descarga de la lógica de control y la manipulación de la configuración del controlador"
    }
  ],
  "lastModified": "2026-06-17T04:43:29.333",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:honeywell:saia_pg5_controls_suite:-:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "3F7830BF-FD3B-4932-9713-CD8F9DB0A167"
            }
          ],
          "operator": "OR"
        }
      ]
    }
  ],
  "sourceIdentifier": "cve@mitre.org"
}