CVE-2024-51756

{"id": "CVE-2024-51756", "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"safety": "NOT_DEFINED", "version": "4.0", "recovery": "NOT_DEFINED", "baseScore": 2.3, "automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "LOW", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/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": "PRESENT", "privilegesRequired": "LOW", "modifiedAttackVector": "NOT_DEFINED", "integrityRequirements": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "availabilityRequirements": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subsequentSystemIntegrity": "NONE", "vulnerableSystemIntegrity": "LOW", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "confidentialityRequirements": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "subsequentSystemAvailability": "NONE", "vulnerableSystemAvailability": "LOW", "subsequentSystemConfidentiality": "NONE", "vulnerableSystemConfidentiality": "LOW", "modifiedSubsequentSystemIntegrity": "NOT_DEFINED", "modifiedVulnerableSystemIntegrity": "NOT_DEFINED", "modifiedSubsequentSystemAvailability": "NOT_DEFINED", "modifiedVulnerableSystemAvailability": "NOT_DEFINED", "modifiedSubsequentSystemConfidentiality": "NOT_DEFINED", "modifiedVulnerableSystemConfidentiality": "NOT_DEFINED"}}]}, "published": "2024-11-05T22:15:21.817", "references": [{"url": "https://en.wikipedia.org/wiki/ISO/IEC_8859-1", "source": "security-advisories@github.com"}, {"url": "https://github.com/bytecodealliance/cap-std/commit/dcc3818039761331fbeacbb3a40c542b65b5ebf7", "source": "security-advisories@github.com"}, {"url": "https://github.com/bytecodealliance/cap-std/pull/371", "source": "security-advisories@github.com"}, {"url": "https://github.com/bytecodealliance/cap-std/security/advisories/GHSA-hxf5-99xg-86hw", "source": "security-advisories@github.com"}, {"url": "https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-22"}]}], "descriptions": [{"lang": "en", "value": "The cap-std project is organized around the eponymous `cap-std` crate, and develops libraries to make it easy to write capability-based code. cap-std's filesystem sandbox implementation on Windows blocks access to special device filenames such as \"COM1\", \"COM2\", \"LPT0\", \"LPT1\", and so on, however it did not block access to the special device filenames which use superscript digits, such as \"COM\u00b9\", \"COM\u00b2\", \"LPT\u2070\", \"LPT\u00b9\", and so on. Untrusted filesystem paths could bypass the sandbox and access devices through those special device filenames with superscript digits, and through them provide access peripheral devices connected to the computer, or network resources mapped to those devices. This can include modems, printers, network printers, and any other device connected to a serial or parallel port, including emulated USB serial ports. The bug is fixed in #371, which is published in cap-primitives 3.4.1, cap-std 3.4.1, and cap-async-std 3.4.1. There are no known workarounds for this issue. Affected Windows users are recommended to upgrade."}, {"lang": "es", "value": "El proyecto cap-std est\u00e1 organizado en torno al caj\u00f3n hom\u00f3nimo `cap-std`, y desarrolla librer\u00edas para facilitar la escritura de c\u00f3digo basado en capacidades. La implementaci\u00f3n del sandbox del sistema de archivos de cap-std en Windows bloquea el acceso a nombres de archivos de dispositivos especiales como \"COM1\", \"COM2\", \"LPT0\", \"LPT1\", etc., sin embargo, no bloquea el acceso a los nombres de archivos de dispositivos especiales que utilizan d\u00edgitos en super\u00edndice, como \"COM\u00b9\", \"COM\u00b2\", \"LPT?\", \"LPT\u00b9\", etc. Las rutas del sistema de archivos no confiables podr\u00edan eludir el sandbox y acceder a los dispositivos a trav\u00e9s de esos nombres de archivos de dispositivos especiales con d\u00edgitos en super\u00edndice, y a trav\u00e9s de ellos proporcionar acceso a dispositivos perif\u00e9ricos conectados a la computadora o recursos de red asignados a esos dispositivos. Esto puede incluir m\u00f3dems, impresoras, impresoras de red y cualquier otro dispositivo conectado a un puerto serial o paralelo, incluidos los puertos seriales USB emulados. El error se corrigi\u00f3 en el n.\u00b0 371, que se public\u00f3 en cap-primitives 3.4.1, cap-std 3.4.1 y cap-async-std 3.4.1. No se conocen workarounds para este problema. Se recomienda a los usuarios de Windows afectados que actualicen."}], "lastModified": "2024-11-21T09:45:56.203", "sourceIdentifier": "security-advisories@github.com"}