CVE-2025-53811

{"id": "CVE-2025-53811", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-53811", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2025-08-26T14:02:24.112393Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "cvd@cert.pl", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 4.8, "Automatable": "NOT_DEFINED", "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/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", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "LOW", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "LOW", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "LOW", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "cvd@cert.pl", "affectedData": [{"vendor": "Mosh-Pro", "product": "Mosh-Pro", "versions": [{"status": "affected", "version": "0.0.0", "versionType": "semver", "lessThanOrEqual": "1.3.6"}], "platforms": ["MacOS"], "defaultStatus": "unknown"}]}], "published": "2025-08-26T13:15:32.317", "references": [{"url": "https://cert.pl/en/posts/2025/08/tcc-bypass/", "source": "cvd@cert.pl"}, {"url": "https://moshpro.app/", "source": "cvd@cert.pl"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "cvd@cert.pl", "description": [{"lang": "en", "value": "CWE-276"}]}], "descriptions": [{"lang": "en", "value": "The configuration of Mosh-Pro on macOS, specifically the \"RunAsNode\" fuse enabled, allows a\u00a0local attacker with unprivileged access to execute arbitrary code that inherits Mosh-Pro TCC (Transparency, Consent, and Control) permissions.\u00a0\nAcquired resource access is limited to previously granted permissions by the user. Accessing other resources beyond previously granted TCC permissions will prompt the user for approval in the name of Mosh-Pro, potentially disguising attacker's malicious intent.\u00a0\n\nThis issue was fixed in 1.3.7 version of Mosh-Pro."}, {"lang": "es", "value": "La configuraci\u00f3n de Mosh-Pro en macOS, en concreto la habilitaci\u00f3n de la funci\u00f3n \"RunAsNode\", permite a un atacante local sin privilegios ejecutar c\u00f3digo arbitrario que hereda los permisos TCC (Transparencia, Consentimiento y Control) de Mosh-Pro. El acceso a los recursos adquiridos se limita a los permisos previamente otorgados por el usuario. Acceder a otros recursos que no cumplan con los permisos TCC previamente otorgados solicitar\u00e1 la aprobaci\u00f3n del usuario en nombre de Mosh-Pro, lo que podr\u00eda ocultar las intenciones maliciosas del atacante. Este problema se detect\u00f3 en la versi\u00f3n 1.3.2 de Mosh-Pro. Dado que los autores no respondieron a los mensajes de CNA, se desconoce el estado de la actualizaci\u00f3n."}], "lastModified": "2026-08-31T14:17:13.020", "sourceIdentifier": "cvd@cert.pl"}