CVE-2025-49846

{"id": "CVE-2025-49846", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 4.1, "Automatable": "NOT_DEFINED", "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:P/VC:H/VI:N/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": "PASSIVE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "HIGH", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "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"}}]}, "published": "2025-07-03T17:15:39.613", "references": [{"url": "https://github.com/wireapp/wire-ios/commit/0cff0e4298d87c2c56de07f3fb18d3e8e5a68fa3", "source": "security-advisories@github.com"}, {"url": "https://github.com/wireapp/wire-ios/releases/tag/appstore%2F3.124.1", "source": "security-advisories@github.com"}, {"url": "https://github.com/wireapp/wire-ios/security/advisories/GHSA-pj5p-96xx-hc7m", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-117"}, {"lang": "en", "value": "CWE-532"}]}], "descriptions": [{"lang": "en", "value": "wire-ios is an iOS client for the Wire secure messaging application. From Wire iOS 3.111.1 to before 3.124.1, messages that were visible in the view port have been logged to the iOS system logs in clear text. Wire application logs created and managed by the application itself were not affected, especially not the logs users can export and send to Wire support. The iOS logs can only be accessed if someone had (physical) access to the underlying unlocked device. The issue manifested itself by calling canOpenUrl() and passing an invalid URL object. When iOS then performs the check and fails, it logs the contents to the system log. This is not documented behaviour. Wire released an emergency fix with version 3.124.1. As a workaround, users can reset their iOS device to remove the offending logs. Since Wire cannot access or modify iOS system logs, there's no other workaround other than a reset."}, {"lang": "es", "value": "wire-ios es un cliente iOS para la aplicaci\u00f3n de mensajer\u00eda segura Wire. Desde Wire iOS 3.111.1 hasta versiones anteriores a la 3.124.1, los mensajes visibles en la ventana de visualizaci\u00f3n se registraban en los registros del sistema iOS en texto plano. Los registros de la aplicaci\u00f3n Wire, creados y gestionados por la propia aplicaci\u00f3n, no se vieron afectados, especialmente los registros que los usuarios pueden exportar y enviar al soporte de Wire. Solo se puede acceder a los registros iOS si alguien ten\u00eda acceso (f\u00edsico) al dispositivo desbloqueado subyacente. El problema se manifest\u00f3 al llamar a canOpenUrl() y pasar un objeto URL no v\u00e1lido. Cuando iOS realiza la comprobaci\u00f3n y falla, registra el contenido en el registro del sistema. Este comportamiento no est\u00e1 documentado. Wire public\u00f3 una soluci\u00f3n de emergencia en la versi\u00f3n 3.124.1. Como soluci\u00f3n alternativa, los usuarios pueden restablecer su dispositivo iOS para eliminar los registros problem\u00e1ticos. Dado que Wire no puede acceder ni modificar los registros del sistema iOS, la \u00fanica soluci\u00f3n alternativa es restablecerlos."}], "lastModified": "2025-07-08T16:19:11.700", "sourceIdentifier": "security-advisories@github.com"}