GitPython's Submodule.move() API does not properly handle symbolic links in intermediate path components, allowing an attacker-controlled symlink to redirect a submodule move operation outside the parent repository worktree. This can cause the submodule checkout to be moved to an attacker-selected directory outside the repository, corrupting the repository's index and configuration state. The vulnerability requires the attacker to control the cloned repository and commit a symlink, and the application to call Submodule.move() with a path under that symlink. No code execution or confidentiality impact is demonstrated.
Authlib versions from 0.13 up to 1.7.2 contain a vulnerability in the is_secure_transport() function, which incorrectly allows certain HTTP URLs with a userinfo component to bypass TLS enforcement. This occurs because the function uses a simple string prefix check that can be fooled by URLs like 'http://localhost:80@evil.example/cb', where the actual host is not a loopback address but an external domain. This flaw affects OAuth 2.0 and OIDC endpoint and redirect URI validation, potentially allowing cleartext HTTP URLs to be accepted as secure in contexts such as OIDC RP-Initiated Logout and authorization server metadata validation. The severity is rated low and a fix is available in Authlib version 0.24.0.
A vulnerability in filelock's ReadWriteLock and AsyncReadWriteLock components allows a local user with write permissions in the directory containing the SQLite lock database to manipulate lock behavior. By planting symlinks or journal-related side files, the attacker can cause the lock user to write arbitrary data into their own files, create or unlink files, or cause lock acquisition failures. This affects filelock versions 3.20.4 through 4.2.0, with the /proc/self/fd redirect introduced in 4.0.9 and side-file handling since 3.20.4. The issue requires a writable directory without the sticky bit and local user access. The CVSS 3.1 score is 7.1 (High), reflecting local attack with low complexity, no confidentiality impact, but high integrity and availability impact.
MadApe is a sophisticated multi-stage phishing campaign targeting Microsoft Device Code authentication. It uses business-themed PDF lures, configurable redirect chains, and fake document-sharing pages impersonating services like SharePoint, OneDrive, Teams, Adobe Acrobat, and DocuSign. The campaign abuses Microsoft's Device Code flow to access victim accounts without credential theft on phishing pages. It features extensive infrastructure with 155 domains, human-verification challenges, decoy sites, and exposed operator panels. The campaign is localized in at least nine languages and focuses on business communications.
WebToffee Product Import Export for WooCommerce versions 2.5.1 up to but not including 2.6.8 contains a server-side request forgery (SSRF) vulnerability. This flaw exists in the download_remote_file function and allows users with shop_manager privileges to submit a CSV URL that triggers an HTTP 302 redirect to internal network addresses. The server then fetches internal responses and returns them as import data, potentially exposing internal services.
Multiple critical security vulnerabilities have been identified in Apache Tomcat versions ranging from early milestone releases through recent stable versions up to 11.0.26, 10.1.60, and 9.0.122. These include authentication bypass, request/response mix-up in HTTP/2 asynchronous servlets, failure to securely enforce FIPS mode, execution after redirect, local unauthorized access via a TOCTOU race condition in unix domain sockets, and incomplete cleanup issues causing information leaks and TLS 1.3 connection failures. Users are strongly recommended to upgrade to fixed versions 11.0.27, 10.1.61, or 9.0.123 to address these vulnerabilities.
Apache CouchDB versions 3.5.2 and earlier contain a vulnerability in the replicator component where it follows HTTP redirects indefinitely due to a missing circuit-breaker. This flaw allows the owner of a replication source or target to cause a denial of service by creating an infinite HTTP redirect loop. The issue is fixed in version 3.5.3.