Pandora vulnerabilities

Pandora contains a path traversal vulnerability in its archive extraction worker. When processing a specially crafted archive or disk image, attacker-controlled file paths could be used without ensuring that the resulting destination remained within the intended extraction directory. An attacker able to submit a malicious file for analysis could use path traversal sequences or crafted paths to cause extracted content to be written outside the designated extraction directory, potentially overwriting files accessible to the Pandora worker process.

Pandora contains a path traversal vulnerability in its TAR archive extraction functionality. When processing a TAR archive, member names are passed directly to Python's tarfile.TarFile.extract() without an extraction filter. An attacker can submit a crafted TAR archive with malicious paths, allowing files to be written outside the intended directory.

Pandora contains a stored XSS vulnerability in the rendering of URL observables. A malicious URL can be injected into the inline JavaScript onclick handler, allowing arbitrary JavaScript execution in the application context.

Pandora is affected by a stored XSS vulnerability in the PDF download functionality. The /task-download/<task_id>/.../pdf endpoint verifies the file is a PDF but returns it without explicit MIME type, allowing it to be served as HTML or another active format. A crafted PDF/polyglot can execute script in the Pandora application context.

Pandora contains a denial-of-service vulnerability in its handling of DAA (Direct Access Archive) files. When extracting the internal ISO image, compressed chunks are decompressed using zlib.decompress() without enforcing a limit on the resulting uncompressed data. An attacker can submit a crafted DAA file with highly compressed data, causing excessive memory and CPU consumption, potentially making the extraction worker unresponsive or terminating it, affecting service availability.