CVE-2025-61785

{"id": "CVE-2025-61785", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-61785", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2025-10-08T18:59:00.429362Z"}}], "cvssMetricV30": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.0", "baseScore": 3.3, "attackVector": "LOCAL", "baseSeverity": "LOW", "vectorString": "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 1.8}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 3.3, "attackVector": "LOCAL", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 1.8}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "denoland", "product": "deno", "versions": [{"status": "affected", "version": ">= 2.3.0, < 2.5.3"}, {"status": "affected", "version": "< 2.2.15"}]}]}], "published": "2025-10-08T01:15:32.847", "references": [{"url": "https://github.com/denoland/deno/commit/992e998dfe436cdc9325232759af8be92f11739b", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/denoland/deno/pull/30872", "tags": ["Issue Tracking", "Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/denoland/deno/releases/tag/v2.2.15", "tags": ["Release Notes"], "source": "security-advisories@github.com"}, {"url": "https://github.com/denoland/deno/releases/tag/v2.5.3", "tags": ["Release Notes"], "source": "security-advisories@github.com"}, {"url": "https://github.com/denoland/deno/security/advisories/GHSA-vg2r-rmgp-cgqj", "tags": ["Exploit", "Vendor Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-266"}]}], "descriptions": [{"lang": "en", "value": "Deno is a JavaScript, TypeScript, and WebAssembly runtime. In versions prior to 2.5.3 and 2.2.15, `Deno.FsFile.prototype.utime` and `Deno.FsFile.prototype.utimeSync` are not limited by the permission model check `--deny-write=./`. It's possible to change to change the access (`atime`) and modification (`mtime`) times on the file stream resource even when the file is opened with `read` only permission (and `write`: `false`) and file write operations are not allowed (the script is executed with `--deny-write=./`). Similar APIs like `Deno.utime` and `Deno.utimeSync` require\u00a0`allow-write`\u00a0permission, however, when a file is opened, even with read only flags and deny-write permission, it's still possible to change the access (`atime`) and modification (`mtime`) times, and thus bypass the permission model. Versions 2.5.3 and 2.2.15 fix the issue."}, {"lang": "es", "value": "Deno es un entorno de ejecuci\u00f3n de JavaScript, TypeScript y WebAssembly. En versiones anteriores a la 2.5.3 y 2.2.15, 'Deno.FsFile.prototype.utime' y 'Deno.FsFile.prototype.utimeSync' no est\u00e1n limitadas por la verificaci\u00f3n del modelo de permisos '--deny-write=./'. Es posible cambiar los tiempos de acceso ('atime') y modificaci\u00f3n ('mtime') en el recurso de flujo de archivo incluso cuando el archivo se abre con permiso de solo lectura ('read' only permission) (y 'write': 'false') y las operaciones de escritura de archivos no est\u00e1n permitidas (el script se ejecuta con '--deny-write=./'). APIs similares como 'Deno.utime' y 'Deno.utimeSync' requieren permiso de 'allow-write', sin embargo, cuando se abre un archivo, incluso con banderas de solo lectura y permiso de denegaci\u00f3n de escritura, todav\u00eda es posible cambiar los tiempos de acceso ('atime') y modificaci\u00f3n ('mtime'), y as\u00ed eludir el modelo de permisos. Las versiones 2.5.3 y 2.2.15 corrigen el problema."}], "lastModified": "2026-10-08T13:10:00.200", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:deno:deno:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "E75979F4-50DD-41E8-932A-C576F86DBFCF", "versionEndIncluding": "2.2.15"}, {"criteria": "cpe:2.3:a:deno:deno:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "7DD66938-204A-4542-BA86-274BB232C8C9", "versionEndExcluding": "2.5.3", "versionStartIncluding": "2.3.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}