CVE-2026-48772— ProxySQL 信任管理问题漏洞

ProxySQL: PROXY-Protocol-v1 UNKNOWN parses spoofed source IP, bypassing mysql_query_rules.client_addr ACL

ProxySQL is a proxy for MySQL and its forks, as well as PostgreSQL. In versions 2.0.0 through 3.0.8, the ProxySQL MySQL frontend accepts the `PROXY UNKNOWN <addr> <addr> <port> <port>\r\n` PP1 frame as a well-formed PROXY protocol header. The HAProxy PROXY protocol v1 specification says that when the protocol token is `UNKNOWN`, the receiver MUST ignore any address fields that follow it, because the proxy has declared it cannot determine the client identity. ProxySQL parses those address fields anyway via `sscanf` and writes the spoofed source address into the session's `addr.addr` field. From there it flows directly into the query-rule matcher, where the `client_addr` predicate decides routing and ACL. When `mysql-proxy_protocol_networks = '*'` (the default), any TCP peer can send a PP1 frame and choose any source IP claim. With that, any `mysql_query_rules` row pinned to a `client_addr` value is forgeable: the attacker writes the address they want to match into the PP1 line, and ProxySQL routes their query as if it came from that address. In practice this is a routing and ACL bypass. Real deployments use `client_addr` for read-write splitting (internal apps go to the primary, public traffic to read replicas), per-app schema pinning, and query-filter rules (DDL allowed only from admin CIDR, public queries blocked from dangerous patterns). An attacker that can reach the frontend port can forge their way into any of those routes. Version 3.0.9 patches this issue.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

使用不可信的源

ProxySQL 信任管理问题漏洞

ProxySQL ProxySQL是ProxySQL组织开源的一个面向MySQL、PostgreSQL及其生态系统的领先数据库代理，支持高性能连接管理、高可用故障转移和实时查询分析。 ProxySQL 2.0.0版本至3.0.8版本存在安全漏洞，该漏洞源于ProxySQL MySQL前端错误地将`PROXY UNKNOWN`协议帧作为有效PROXY协议标头解析，通过`sscanf`将伪造的源地址写入session的`addr.addr`字段，导致`client_addr`路由和ACL可被绕过，攻击者可通过

N/A

N/A