A vulnerability in GStreamer's gst-plugins-bad H.266/VVC parser allows a crafted malformed media file or stream to trigger an integer overflow during parsing of profile, tier, and level fields. This overflow can lead to a stack-based buffer overflow, potentially causing application crashes or enabling code execution with the application's privileges. The flaw affects certain versions of gstreamer1-plugins-bad-free in Red Hat Enterprise Linux 10.2.z, 10.3.z, 10.4, RHIVOS 2.1 and 2.1-core, and Fedora 43. No complete mitigation or fix is currently available, and users are advised to disable H.266/VVC media ingestion or avoid processing untrusted H.266/VVC content until patched.
A heap out-of-bounds access vulnerability exists in Blender versions before 4.5.15 and 5.x before 5.2.3 in the read_struct() function. This flaw occurs because size validation is skipped when a .blend file's SDNA struct layout compares equal, allowing crafted .blend files with short blocks to cause heap memory overruns. Such overruns can lead to application crashes or potentially arbitrary code execution.
Blender versions before 4.5.15 and 5.x before 5.2.3 contain a heap buffer overflow vulnerability caused by an integer overflow in the ptcache_data_alloc() function when reading point cache files. An attacker can supply a crafted point cache file with a large totpoint value alongside a .blend file to cause a crash or execute arbitrary code with the user's privileges.
A heap buffer overflow vulnerability exists in Blender versions before 4.5.15 and 5.x before 5.2.3. The flaw is caused by a 32-bit integer overflow in the thumb_data_vertical_flip() function used by the blend file thumbnail extractor. Maliciously crafted .blend files with specially designed TEST block dimensions can trigger out-of-bounds writes when previewed by blender-thumbnailer or the Windows shell extension, potentially leading to crashes or arbitrary code execution.
Scribus versions prior to 1.6.7 have an out-of-bounds memory access vulnerability in the importsvm plugin. This flaw occurs because the plugin does not verify that bitmap and transparency mask dimensions match when importing SVM files. An attacker can craft a malicious SVM file with mismatched mask dimensions to trigger heap reads and writes, potentially causing application crashes or arbitrary code execution with the privileges of the user running Scribus.
Scribus versions before 1.6.7 have a heap buffer overflow vulnerability in the Mac PICT image loader and import plugin. This occurs when unpacking 4-bit indexed pixel data from a crafted PICT file with inconsistent width and row data. Exploitation can cause application crashes or potentially allow code execution.
Scribus versions prior to 1.6.7 contain an out-of-bounds write vulnerability in the importdrw Micrografx Draw plugin. This flaw arises from using an unvalidated y offset to select image scanlines, allowing crafted DRW files to write decoded bitmap data outside the intended heap buffer. This can lead to application crashes or potential code execution when a user imports a malicious file.
Scribus versions prior to 1.6.7 have a heap out-of-bounds write vulnerability in the scimgdataloader_psd loader. This flaw arises from using unchecked PSD file values as array indexes, which can lead to heap memory corruption. An attacker can exploit this by convincing a user to open or import a specially crafted PSD file, potentially causing application crashes or arbitrary code execution with the user's privileges.
A vulnerability was determined in 37954679 cak-filemanagement-system up to 5e6433246475e66462e1fea980688de96a049297. This vulnerability affects the function move_uploaded_file of the file admin/add_logs.php. Executing a manipulation of the argument File can lead to unrestricted upload. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.
The gettext family of functions in the GNU C Library version 2.0 and later accept LANGUAGE environment variable entries that contain '/' or that are equal to "..", unless the program is setuid or setgid (AT_SECURE). An attacker who can set LANGUAGE in the environment of a program that uses gettext can make it load a message catalog (.mo file) from an arbitrary location in the file system. A crafted .mo file can crash the program through out-of-range offsets, or supply translations whose format directives do not match the arguments passed by the program. That causes undefined behaviour in the printf family of functions and may allow arbitrary code execution with the privileges of the program. The safety of message catalogs relies on them being installed in trusted, read-only locations, and the directory traversal bypasses this.
The fix for CVE-2014-0475 rejects ".." path components in locale names passed to setlocale or taken from the LC_ALL, LC_* and LANG environment variables. gettext reads LANGUAGE directly and appends each colon-separated entry to the message catalog directory, so that fix did not cover LANGUAGE.
LANGUAGE is only used when the LC_MESSAGES locale is not "C", "C.<encoding>" or "POSIX", so the attacker must also be able to select another installed locale, for example through LANG or LC_ALL. Exploitation also requires that the attacker can place the crafted file in a location readable by the target program, and that the environment crosses a trust boundary without the program running as AT_SECURE. An example is an SSH server that accepts LANGUAGE and LANG from clients through the AcceptEnv directive and restricts an account to a forced command; the attacker may use this to escape the restriction.
FlowiseAI Flowise versions up to 3.1.4 contain a sandbox escape vulnerability that allows authenticated users to execute arbitrary OS commands. This occurs when the ALLOW_BUILTIN_DEP environment variable is set to true, enabling abuse of allowlisted langchain and mammoth modules. Attackers can submit JavaScript code to the /api/v1/node-custom-function endpoint, which writes a file into the mammoth package via LocalFileStore and requires it, thereby escaping the vm2 sandbox with the privileges of the Flowise process user.
Mythic versions 3.2.16 through 3.4.0.61 contain a stored cross-site scripting (XSS) vulnerability. Attackers can embed malicious HTML in files named with a .pdf extension. When an operator previews such a file in the Mythic UI, the malicious script executes in the same origin, allowing theft of localStorage JWT tokens. These tokens grant full GraphQL and REST API access, potentially compromising the system.
The Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.4.1 via the legacy_render function. This is due to broken authorization on the Lightroom gallery_edit endpoint combined with mass assignment of gallery path and unrestricted file upload into a registered template directory, whose extension check uses a substring match that accepts sanitized .php_ filenames as valid templates. This makes it possible for authenticated attackers, with custom-level access and above, to execute code on the server. Exploitation requires the authenticated attacker to be the stored author of at least one existing NextGEN gallery, as ownership of that gallery is the sole authorization check gating the mass-assignment and upload steps.
The Avada | Website Builder For WordPress & WooCommerce theme for WordPress is vulnerable to Arbitrary File Upload in versions up to, and including, 7.16.2 via the convert_palette_images_to_truecolor() function. This is due to insufficient file type validation before processing uploaded files. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible.
The JS Help Desk – AI-Powered Support & Ticketing System plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the setSupportCustomImage function in all versions up to, and including, 5.0.1. This makes it possible for authenticated attackers, with administrator-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). Exploitation requires a two-step sequence: an administrator first saves a traversal-crafted value in the support_custom_img configuration field, then triggers deletion by uploading a new support custom image, at which point setSupportCustomImage() resolves and deletes the attacker-controlled path.