CVE-2025-61235

{"id": "CVE-2025-61235", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-61235", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2025-10-29T13:55:12.645267Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "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:H/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "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": "2025-10-28T20:15:49.500", "references": [{"url": "https://github.com/stuxve/poc-dataphone-crafted-packet", "source": "cve@mitre.org"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-20"}]}], "descriptions": [{"lang": "en", "value": "An issue was discovered in Dataphone A920 v2025.07.161103. A custom packet based on public documentation can be crafted, where some fields can contain arbitrary or trivial data. Normally, such data should cause the device to reject the packet. However, due to a lack of validation, the device accepts it with no authetication and triggers the functionality instead."}, {"lang": "es", "value": "Se descubri\u00f3 un problema en Dataphone A920 v2025.07.161103. Se puede forjar un paquete personalizado basado en documentaci\u00f3n p\u00fablica, donde algunos campos pueden contener datos arbitrarios o triviales. Normalmente, dichos datos deber\u00edan hacer que el dispositivo rechace el paquete. Sin embargo, debido a una falta de validaci\u00f3n, el dispositivo lo acepta sin autenticaci\u00f3n y en su lugar activa la funcionalidad."}], "lastModified": "2026-11-05T21:10:00.183", "sourceIdentifier": "cve@mitre.org"}