CERT Recently Published Vulner... Note

CERT Recently Published Vulnerability Notes

kb.cert.org/vuls is a webpage maintained by the Carnegie Mellon University Software Engineering Institute (SEI) which provides a publicly accessible database of known software vulnerabilities. It lists a vast amount of vulnerability information including identifiers, descriptions, severity ratings, and potential impacts, helping users stay informed about potential security risks.

Thread Of Notes

The Kaltura HTML5 Player Library, specifically versions html5lib v2.45, v2.103 and earlier, contains two critical vulnerabilities. Both stem from an insecure deserialization flaw within the mwEmbedLoader.php endpoint. This endpoint allows user-controlled ServiceUrl parameters for backend API requests. The internal KalturaClientBase PHP library fetches data from this URL and deserializes it without validation.CVE-2026-19913 allows arbitrary file reads by exploiting the deserialization flaw and improper error handling. An attacker can provide a file:// path to ServiceUrl, causing the player to fetch and attempt to deserialize local file contents. Failed deserialization reflects raw bytes in error messages, revealing sensitive file data.CVE-2026-19912 enables remote code execution due to insufficient sanitization of the uiconf_id parameter. This parameter controls file write locations, allowing directory traversal attacks. An attacker can craft a malicious serialized object with executable PHP code and redirect its deserialized fields to a web-accessible directory.Exploiting these vulnerabilities requires only network access to the affected endpoint; no authentication is needed. Successful attacks can lead to the theft of sensitive information like credentials or API keys. Remote code execution allows for data manipulation, persistence, and further system compromise. These vulnerabilities also affect tenants on Kaltura's shared CDN infrastructure.Until a vendor patch is released, users should restrict or disable external access to mwEmbedLoader.php. Implementing a strict allow-list for ServiceUrl to permit only legitimate API URLs is also recommended.
A vulnerability has been discovered in Develar's app-builder, a command-line build tool used to package and distribute application bundles for macOS, Windows, and Linux. The issue arises from a combination of Unicode normalization collisions and unsafe symlink-following behavior in the zipx.Unzip extraction routine. This allows an attacker to overwrite arbitrary files on macOS systems using Apple File System (APFS) by crafting ZIP archives that combine Unicode normalization collisions with malicious symlinks. The vulnerability is exploitable during ZIP extraction without requiring elevated privileges and can result in loss of integrity, denial of service, or potential code execution. Develar's app-builder is widely used as a dependency across the ecosystem, affecting numerous downstream repositories, and several projects have already mitigated their exposure. A complete remediation requires fixing the vulnerability at its source, and a GitHub Pull Request has been developed to provide downstream customers with a reference fix. The Pull Request addresses the symlink-following variant of the vulnerability by rejecting any symlink whose resolved target escapes the intended output directory and by adding O_NOFOLLOW to regular file writes. The reporter, Tomas Illuminati, has assisted many downstream vendors and developers in mitigating this issue, and Electron-Userland has responded quickly and implemented a mitigation to protect their downstream users. The vulnerability can be exploited by combining Unicode normalization collisions with symlink-following behavior, allowing an attacker to bypass path-validation checks and redirect writes outside the intended extraction directory. The CERT/CC has prepared a vulnerability note to inform users of the issue and provide guidance on mitigation and remediation. Overall, the vulnerability has significant implications for the security of macOS systems using APFS, and users are advised to take steps to mitigate their exposure.
Two critical cryptographic signature verification vulnerabilities exist in the widely used node-forge JavaScript library. These flaws allow attackers to forge RSA (PKCS#1 v1.5) and Ed25519 signatures under specific circumstances. The RSA vulnerability, CVE-2026-33894, arises from accepting non-canonical ASN.1 encodings and undersized padding during signature verification. This enables attackers to craft signatures that node-forge validates but standard libraries reject, especially with low public exponents. The Ed25519 vulnerability, CVE-2026-33895, stems from failing to enforce scalar canonicality, allowing signatures with non-canonical scalars to be accepted. This undermines signature uniqueness and enables substitution attacks. Affected versions range from 0.1.2 through 1.3.3 for RSA and 0.7.4 through 1.3.3 for Ed25519. The primary impact is the ability for attackers to bypass authentication, code-signing, or token validations. Applications using default node-forge verification APIs, including popular JOSE libraries, are potentially exposed. Exploitation is straightforward and can occur over the network. Version 1.4.0, released on 2026-04-05, fully addresses these issues by enforcing strict canonical validation for both RSA and Ed25519 signatures. Users are strongly advised to upgrade to this version to patch the vulnerabilities. If immediate upgrading is not feasible, recommended mitigations include auditing call sites and falling back to Node.js native crypto verification.
Adalo's no-code application platform has a significant security flaw that exposes complete user records through its database API for all applications built on both V1 and V2. This issue affects over one million applications, putting developers and their end users at risk of data exposure. The problem arises from a platform-level flaw that allows authenticated users to retrieve full user data belonging to any Adalo application, regardless of configuration. Adalo is a Software-as-a-Service provider for building no-code applications, and each application is supposed to be logically isolated with separate databases, users, and configurations. However, the Adalo database API contains a flaw that allows the backend to return complete user records for every list component request, regardless of which fields the component is configured to display. The database does not enforce ownership-aware, server-side authorization checks, allowing authenticated users of any Adalo application to query database and table identifiers belonging to other applications and retrieve full records. Additionally, Adalo's use of long-lived JWT tokens, which remain valid for approximately twenty days, allows attackers to reuse these tokens to query the database API directly and extract large volumes of user data. The combination of exposed tokens, permissive CORS behavior, and large response limits enables persistent, automated harvesting of entire user databases using only a single token obtained from any visitor session. The vulnerabilities affect all Adalo applications across both V1 and V2, and customers and tenants should assume that data in Adalo collections may be exposed and avoid storing sensitive information there until a patch is deployed. Adalo has acknowledged the issue, but no patch is currently available, and users should remain aware of increased phishing and identity theft risks and monitor their accounts for suspicious activity.
Microsoft is revoking trust for older versions of the open-source shim bootloader due to a Secure Boot bypass vulnerability. This vulnerability allows attackers to execute arbitrary code early in the boot process, circumventing security measures. The affected shim bootloaders, primarily versions 0.9 and earlier, will be added to the Microsoft UEFI Forbidden Signature Database (DBX). Once the DBX is updated, these bootloaders will be disallowed from running.The shim project facilitates Secure Boot for Linux distributions by acting as a bridge between firmware and the operating system. However, vendors who forked older, vulnerable versions without updating created a persistent supply chain risk. Researchers identified specific vulnerable shim bootloaders from various vendors, including Red Hat, baramundi, and Oracle.Exploiting this flaw enables attackers with boot modification privileges to gain persistent control, potentially loading unsigned kernel components that survive reboots. These malicious components can evade operating system security and endpoint detection solutions. To mitigate this, users must apply the latest vendor software and bootloader updates.Additionally, applying Microsoft's DBX update is crucial to block vulnerable bootloaders. Enterprises and developers should test these updates thoroughly before widespread deployment. It is recommended to update the authorized signature database (DB) before applying DBX revocations. Tools are available to audit and verify DBX updates and identify revoked boot components.
The PCTCore64.sys Windows kernel driver from PC Tools Internet Security has a significant security vulnerability. This driver exposes a device interface called \.\PCTCoreDriver without proper access control measures in place. Consequently, any user-mode process can interact with this driver and execute privileged IOCTL commands.In a Bring Your Own Vulnerable Driver (BYOVD) scenario, an attacker with the ability to load a Windows driver can exploit this flaw. They can perform sensitive low-level operations on the target system by invoking the driver's exposed interface. The driver lacks secure descriptor application, allowing unprivileged processes to open device handles and send privileged IOCTL requests.This allows attackers to perform actions like enumerating system-wide handles and manipulating handles across processes. Crucially, it enables credential extraction from sensitive processes like lsass.exe. Arbitrary process termination, including protected processes, is also possible.Although PC Tools Internet Security was discontinued in 2013, the driver remains signed and exploitable in BYOVD attacks. This vulnerability facilitates credential theft, disabling security software, and achieving broader system compromise. The impact includes credential theft, denial-of-service, and system compromise.The solution is to remove and block the vulnerable driver, as it is no longer maintained. Organizations should also implement mitigations against BYOVD attacks, such as restricting admin privileges and enabling Windows security features like HVCI and WDAC.