CVE-2024-27308

{"id": "CVE-2024-27308", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "published": "2024-03-06T20:15:47.730", "references": [{"url": "https://github.com/tokio-rs/mio/commit/90d4fe00df870acd3d38f3dc4face9aacab8fbb9", "source": "security-advisories@github.com"}, {"url": "https://github.com/tokio-rs/mio/pull/1760", "source": "security-advisories@github.com"}, {"url": "https://github.com/tokio-rs/mio/security/advisories/GHSA-r8w9-5wcg-vfj7", "source": "security-advisories@github.com"}, {"url": "https://github.com/tokio-rs/tokio/issues/6369", "source": "security-advisories@github.com"}, {"url": "https://github.com/tokio-rs/mio/commit/90d4fe00df870acd3d38f3dc4face9aacab8fbb9", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/tokio-rs/mio/pull/1760", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/tokio-rs/mio/security/advisories/GHSA-r8w9-5wcg-vfj7", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/tokio-rs/tokio/issues/6369", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-416"}, {"lang": "en", "value": "CWE-672"}]}], "descriptions": [{"lang": "en", "value": "Mio is a Metal I/O library for Rust. When using named pipes on Windows, mio will under some circumstances return invalid tokens that correspond to named pipes that have already been deregistered from the mio registry. The impact of this vulnerability depends on how mio is used. For some applications, invalid tokens may be ignored or cause a warning or a crash. On the other hand, for applications that store pointers in the tokens, this vulnerability may result in a use-after-free. For users of Tokio, this vulnerability is serious and can result in a use-after-free in Tokio. The vulnerability is Windows-specific, and can only happen if you are using named pipes. Other IO resources are not affected. This vulnerability has been fixed in mio v0.8.11. All versions of mio between v0.7.2 and v0.8.10 are vulnerable. Tokio is vulnerable when you are using a vulnerable version of mio AND you are using at least Tokio v1.30.0. Versions of Tokio prior to v1.30.0 will ignore invalid tokens, so they are not vulnerable. Vulnerable libraries that use mio can work around this issue by detecting and ignoring invalid tokens."}, {"lang": "es", "value": "Mio es una librer\u00eda Metal I/O para Rust. Cuando se utilizan canalizaciones con nombre en Windows, mio, en algunas circunstancias, devolver\u00e1 tokens no v\u00e1lidos que corresponden a canalizaciones con nombre que ya se han dado de baja del registro de mio. El impacto de esta vulnerabilidad depende de c\u00f3mo se utilice mio. Para algunas aplicaciones, los tokens no v\u00e1lidos pueden ignorarse o provocar una advertencia o un bloqueo. Por otro lado, para las aplicaciones que almacenan punteros en tokens, esta vulnerabilidad puede resultar en un use-after-free para los usuarios de Tokio, esta vulnerabilidad es grave y puede resultar en un use-after-free en Tokio. La vulnerabilidad es espec\u00edfica de Windows y solo puede ocurrir si utiliza canalizaciones con nombre. Otros recursos de IO no se ven afectados. Esta vulnerabilidad se ha solucionado en mio v0.8.11. Todas las versiones de mio entre v0.7.2 y v0.8.10 son vulnerables. Tokio es vulnerable cuando est\u00e1s usando una versi\u00f3n vulnerable de mio Y est\u00e1s usando al menos Tokio v1.30.0. Las versiones de Tokio anteriores a la v1.30.0 ignorar\u00e1n los tokens no v\u00e1lidos, por lo que no son vulnerables. Las bibliotecas vulnerables que utilizan mio pueden solucionar este problema detectando e ignorando tokens no v\u00e1lidos."}], "lastModified": "2024-11-21T09:04:17.800", "sourceIdentifier": "security-advisories@github.com"}