Executive brief
Kozou, a tool that turns database schemas into APIs and admin interfaces, contained several security weaknesses in its default configuration. These flaws could allow attackers to crash the service by sending large amounts of data, bypass security restrictions via malicious websites (DNS rebinding), or perform unauthorized database changes through simple web requests. In some cases, unauthenticated interfaces were exposed to the entire internet by default, potentially allowing unauthorized access to sensitive data or functions.
Technical details
Kozou versions 1.8.0 and earlier suffer from four primary security issues. First, the MCP HTTP server lacks Host/Origin validation, making it susceptible to DNS-rebinding attacks that allow malicious websites to interact with the unauthenticated loopback service. Second, both MCP and REST servers lack request-body size limits, leading to potential memory exhaustion (DoS). Third, HTTP GET requests were incorrectly executed in read/write transactions, potentially allowing data modification via volatile functions or writable views. Finally, default Docker configurations bound unauthenticated services to all interfaces (0.0.0.0) instead of loopback. These issues are addressed in version 1.8.1 by implementing Host validation, request-body caps, READ ONLY transactions for GET requests, and loopback-by-default binding.
Affected products
- kozou-dev kozou <= 1.8.0
- kozou-dev @kozou/api <= 1.8.0
- kozou-dev @kozou/mcp <= 1.8.0
- kozou-dev @kozou/core <= 1.8.0
Timeline
- 2026-06-16: disclosed
- 2026-06-19: advisory
- 2026-06-19: patched