It was discovered that dpkg-deb does not properly sanitize directory permissions when extracting a control member into a temporary directory, which is
documented as being a safe operation even on untrusted data. This may result in leaving temporary files behind on cleanup. Given automated and repeated execution of dpkg-deb commands on
adversarial .deb packages or with well compressible files, placed
inside a directory with permissions not allowing removal by a non-root
user, this can end up in a DoS scenario due to causing disk quota
exhaustion or disk full conditions.
Se descubrió que dpkg-deb no depura correctamente los permisos de directorio al extraer un miembro de control a un directorio temporal, lo cual se documenta como una operación segura incluso con datos no confiables. Esto puede resultar en la pérdida de archivos temporales durante la depuración. Si se ejecutan comandos dpkg-deb de forma automatizada y repetida en paquetes .deb adversarios o con archivos bien comprimibles, ubicados dentro de un directorio con permisos que impiden la eliminación por parte de un usuario no root, esto puede provocar un ataque de denegación de servicio (DoS) al causar el agotamiento de la cuota de disco o la saturación del disco.
It was discovered that dpkg-deb does not properly sanitize directory permissions when extracting a control member into a temporary directory, which is documented as being a safe operation even on untrusted data. This may result in leaving temporary files behind on cleanup. Given automated and repeated execution of dpkg-deb commands on adversarial .deb packages or with well compressible files, placed inside a directory with permissions not allowing removal by a non-root user, this can end up in a DoS scenario due to causing disk quota exhaustion or disk full conditions.
