SQL Injection in Oracle Escalates to SYSTEM Execution on Windows via Embedded Java Compilation
A real-world intrusion chain observed in active attacks shows how a simple SQL injection can escalate to full command execution on Windows with SYSTEM privileges. The pivot relies on Oracle Database and its built-in capability to load, compile, and execute Java inside the database engine, a powerful feature that significantly expands the attack surface when left enabled without proper controls.
The intrusion began with a basic SQL injection in an internet-facing application and progressed to command execution on a Windows server under SYSTEM rights. The critical turning point was not a new operating-system vulnerability but a legitimate Oracle Database function that allows Java source code to be loaded, compiled, and executed as part of the database's internal logic.
After obtaining database access, the attackers inserted Java source code, turned it into schema objects, and compiled it directly on the server. This post-exploitation method is particularly challenging for defenders because it reduces dependence on classic on-disk binaries and moves tooling inside the database engine, which is often monitored less rigorously than the operating system or web server.
The activity has been associated with an artifact named khunt, linked to telemetry from Huntress. The ultimate goal is to convert an application-level entry point into a pathway for executing actions on the host. When the Oracle process runs with elevated permissions on Windows, any execution chained from the database context can inherit very high privileges, up to SYSTEM, posing severe risks to the rest of the machine and its data.
The chain reinforces a well-known but frequently ignored principle: defense must start at the application layer. Remediation requires replacing string concatenation with parameterized queries and strict input validation. Database administrators should then evaluate whether Java support in Oracle is truly necessary; if not, it should be disabled or heavily restricted.
Security teams can improve visibility by monitoring specific signals inside Oracle, including statements and events such as CREATE JAVA SOURCE, CREATE JAVA CLASS, and compilation operations. Additional hardening steps include limiting users who can execute Java-related DDL, applying least-privilege principles to the application database account, and preventing the Oracle service from running with unnecessary Windows privileges.
Related articles
Fuzzy Logic in Cybersecurity: Reducing Vulnerability Queue by 7.5 Times with CVSS, EPSS and FSTEC Comparison
An information security specialist has developed a fuzzy logic system that prioritizes vulnerabilities far more effectively than traditional scoring methods. The approach uses linguistic variables and membership functions to handle the inherent uncertainty in exploitability and impact assessments. By integrating EPSS probability data with CVSS impact scores and vulnerability age, the model reduces the actionable backlog by a factor of 7.5. The implementation relies on the Mamdani inference algorithm and trapezoidal membership functions to produce smooth, human-interpretable urgency ratings. Detailed coverage checks and rule-base validation ensure no gaps exist in the decision space. Real-world testing on CVE-2025-49113 in Roundcube Webmail demonstrated practical advantages over rigid threshold logic. The method is positioned as a practical enhancement rather than a replacement for existing standards.
VLC Media Player Hit by Two Memory Corruption Flaws Exploitable via Malicious PNG and Rogue RealRTSP Server
Two vulnerabilities have been discovered in the VLC media player that allow out-of-bounds memory access. The issues affect versions from 3.0.0 through 3.0.23. CVE-2026-56711, rated 8.6 on CVSS 4.0, stems from an integer overflow when calculating image buffer sizes in PNG files, enabling attackers to trigger writes beyond allocated memory simply by opening a crafted image or loading it from a playlist. CVE-2026-73324, scored 6.9, resides in the RealRTSP module and permits a malicious server to send an oversized response string that causes reads past the end of a buffer due to a missing null terminator. Both flaws are present in official VideoLAN builds, although some distributions may exclude the RealRTSP component. No special configuration or plugins are required to trigger the issues. Until patched releases appear, users are advised to avoid opening images or playlists from untrusted sources and to refrain from connecting to unknown RealRTSP streams.
September Windows 11 Security Update KB5124008 Breaks Always On VPN Certificate Authentication
The September security update KB5124008 for Windows 11 has introduced a regression that disables Always On VPN connections using certificate-based authentication. The issue affects devices running Windows 11 versions 24H2 and 25H2 that connect to Remote Routing and Access Service (RRAS) and Network Policy Server (NPS) instances on Windows Server 2019. VPN profiles deployed via Microsoft Intune are impacted, with the failure occurring during the certificate negotiation phase of the IPsec connection. Users confirm the problem is reproducible: the VPN works before the patch, stops after installation, and resumes after patch removal and reboot. Microsoft has not yet acknowledged the regression or released a fix, leaving administrators to pause deployment through WSUS or Intune and open support cases with client and NPS logs. A potential workaround involves switching profiles to EAP-TLS, though its reliability remains unconfirmed.
API Token Lifecycle: From Issuance to Revocation and Secure Management
The article provides a comprehensive examination of the full API token lifecycle in browser-based applications, emphasizing that signatures alone cannot prevent token theft. It details risks introduced at issuance, storage, transmission, and revocation stages, including improper OAuth grant types and long-lived tokens. Key recommendations include short-lived access tokens, atomic refresh token rotation, and the use of Authorization Code Flow with PKCE for public clients. Storage advice strongly discourages localStorage and sessionStorage in favor of HttpOnly cookies or a Backend-for-Frontend pattern that keeps real tokens on the server. The piece also covers CSRF protections, rate limiting on authorization endpoints, and the advantages of signed client assertions over static secrets. Overall, it stresses that token security depends on the entire lifecycle architecture rather than cryptographic strength alone.