Description

Anyquery is an SQL query engine built on top of SQLite. Prior to 0.4.5, anyquery server exposes URL-capable SQLite virtual table modules such as json_reader and log_reader through its unauthenticated MySQL-compatible server port without restricting outbound destinations. A remote attacker can provide a loopback, private-network, or link-local cloud metadata URL, causing go-getter in the Anyquery server process to fetch the selected resource and expose its response as queryable table data. This permits internal network probing, access to internal APIs, and disclosure of cloud credentials; low-integrity impact is possible when a reached internal API performs state-changing actions. This issue is fixed in version 0.4.5.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "8.6",
  "pubDate": "2026-09-14T20:16:46.723Z",
  "pubdate": "2026-09-14T20:16:46.723Z",
  "executiveSummary": "Anyquery prior to version 0.4.5 contains a critical Server-Side Request Forgery (SSRF) vulnerability originating from its MySQL-compatible server port. The vulnerability allows unauthenticated remote attackers to leverage SQLite virtual table modules, specifically json_reader and log_reader, to trigger outbound network requests through the go-getter library used by the server process.\nThe flaw stems from the application's failure to restrict outbound destinations for these modules, permitting access to arbitrary resources including loopback addresses, private-network segments, and link-local cloud metadata services (e.g., 169.254.169.254). By manipulating the server into fetching external or internal resources, an attacker can exfiltrate sensitive data, including cloud credentials and internal API responses, directly into queryable table results. Given the lack of authentication on the server port and the ability to interact with internal network endpoints, the vulnerability poses a significant risk to organizational infrastructure, potentially allowing for internal network scanning and unauthorized state-changing actions against internal services.",
  "technicalDetails": "The vulnerability resides in the Anyquery server's integration of SQLite virtual table modules. Specifically, the json_reader and log_reader modules are exposed through an unauthenticated MySQL-compatible interface. These modules utilize the go-getter library to fetch data from provided URLs, a functionality intended to allow users to query remote files as if they were local tables.\nThe root cause is an insufficient validation of input URLs combined with a lack of egress filtering. Because the Anyquery server does not implement an allow-list or deny-list for network destinations, the go-getter library executes requests on behalf of the server process to any host, including restricted internal network ranges. The attack flow begins with an unauthenticated attacker connecting to the Anyquery MySQL-compatible port. The attacker then executes a crafted SQL query utilizing the vulnerable virtual table modules, passing a targeted URL as an argument. The Anyquery server, acting as a proxy, uses the go-getter utility to retrieve the content of the specified URL. The response retrieved from the internal or cloud-based resource is then parsed by the virtual table module and returned to the attacker as the result set of the SQL query.\nThis mechanism permits several high-impact attack vectors. Attackers can perform blind or data-exfiltrating SSRF by targeting internal services that are otherwise inaccessible from the public internet. By querying cloud metadata endpoints, an attacker can retrieve instance-specific credentials, such as IAM roles or service account tokens, which are frequently exposed via HTTP requests to specific link-local IP addresses. Furthermore, because these modules essentially allow the attacker to perform GET requests against any reachable internal service, they can conduct internal network discovery and mapping. In scenarios where internal APIs are susceptible to state-changing operations via GET requests or where the request body can be manipulated through secondary injection, an attacker may achieve low-integrity impact by influencing the operation of internal systems. The vulnerability affects all versions of Anyquery prior to 0.4.5, and because the MySQL-compatible port is exposed without authentication, the barrier to exploitation is minimal for any attacker with network reachability to the server instance."
}