CVE-2025-42993

{"id": "CVE-2025-42993", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "cna@sap.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.7, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "HIGH", "confidentialityImpact": "HIGH"}, "impactScore": 5.5, "exploitabilityScore": 1.2}]}, "published": "2025-06-10T01:15:22.667", "references": [{"url": "https://me.sap.com/notes/3580384", "source": "cna@sap.com"}, {"url": "https://url.sap/sapsecuritypatchday", "source": "cna@sap.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "cna@sap.com", "description": [{"lang": "en", "value": "CWE-862"}]}], "descriptions": [{"lang": "en", "value": "Due to a missing authorization check vulnerability in SAP S/4HANA (Enterprise Event Enablement), an attacker with access to the Inbound Binding Configuration could create an RFC destination and assign an arbitrary high-privilege user. This allows the attacker to consume events via the RFC destination, leading to code execution under the privileges of the assigned high-privilege user. While the vulnerability has a low impact on Availability, it significantly poses a high risk to both Confidentiality and Integrity."}, {"lang": "es", "value": "Debido a una vulnerabilidad de falta de comprobaci\u00f3n de autorizaci\u00f3n en SAP S/4HANA (Enterprise Event Enablement), un atacante con acceso a la configuraci\u00f3n de enlace entrante podr\u00eda crear un destino RFC y asignar un usuario arbitrario con privilegios altos. Esto le permite consumir eventos a trav\u00e9s del destino RFC, lo que provoca la ejecuci\u00f3n de c\u00f3digo con los privilegios del usuario con privilegios altos asignado. Si bien la vulnerabilidad tiene un impacto bajo en la disponibilidad, representa un riesgo significativo tanto para la confidencialidad como para la integridad."}], "lastModified": "2025-06-12T16:06:39.330", "sourceIdentifier": "cna@sap.com"}