Threat Intelligence Database

Pandora-analysis pandora versions up to 1.12.7 contain a critical path traversal vulnerability in the archive extraction worker. This flaw allows an attacker submitting a malicious archive or disk image to cause files to be extracted outside the intended directory, potentially overwriting system or application files. Exploitation could lead to unauthorized file modification, denial of service, or further system compromise depending on the Pandora process permissions. The vulnerability is addressed by validating resolved extraction paths to ensure they remain within the designated directory and rejecting attempts that traverse outside.

Pandora-analysis pandora versions up to 1.12.5 contain a stored cross-site scripting (XSS) vulnerability in the rendering of URL observables. The vulnerability arises because attacker-controlled URLs are embedded directly into inline JavaScript onclick handlers without proper neutralization, allowing script injection. This can lead to arbitrary JavaScript execution in the context of the Pandora web application when a user interacts with the affected control. A patch has been implemented that removes the vulnerable inline JavaScript usage and replaces it with safer DOM-based handling.

Pandora-analysis pandora versions up to 1.12.5 are affected by a stored cross-site scripting (XSS) vulnerability in the PDF download functionality. The vulnerability arises because the application returns PDF files without explicitly setting the MIME type or forcing downloads as attachments, allowing specially crafted files to be served with an active MIME type. This can lead to execution of attacker-controlled scripts in the context of the Pandora application when a victim accesses the malicious PDF download link. A patch has been implemented to explicitly set the Content-Type to application/pdf, force Content-Disposition to attachment, and assign a trusted .pdf filename based on the task UUID.

Pandora contains a denial-of-service vulnerability in its handling of DAA (Direct Access Archive) files. When extracting the internal ISO image from a DAA archive, compressed chunks were decompressed using zlib.decompress() without enforcing a limit on the resulting uncompressed data. An attacker able to submit a crafted DAA file containing highly compressed data could cause Pandora to decompress a relatively small input into a very large amount of data in memory. Because the decompressed chunks are accumulated to construct the internal ISO image, this could result in excessive memory consumption and potentially CPU exhaustion, causing the extraction worker to become unresponsive, terminate, or affect the availability of the Pandora service. The patch introduces bounded decompression using decompressobj().decompress() with max_extracted_filesize, verifies the cumulative size of decompressed chunks, and raises a dedicated ZipBomb exception when the configured limit is exceeded. Pandora then aborts extraction and reports the file as too large.

Pandora contains a path traversal vulnerability in its TAR archive extraction functionality. When processing a submitted TAR archive, the extractor passed archive member names directly to Python's tarfile.TarFile.extract() without applying an extraction filter. An attacker able to submit a specially crafted TAR archive containing malicious member paths, such as paths using ../ sequences or absolute paths, could cause extracted files to be written outside the intended extraction directory. This may allow the attacker to overwrite files accessible to the Pandora worker process and could potentially result in application compromise, arbitrary code execution, or denial of service depending on the files targeted and the privileges of the Pandora process. The vulnerability is corrected by using Python's filter='data' extraction filter, which rejects or sanitizes dangerous TAR members, including paths that escape the destination directory and unsafe link targets. The weakness corresponds to MITRE's general path traversal category, which includes archive extraction cases where attacker-controlled filenames cause files to be written outside the intended directory.