Jack
70cdb58e94
### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: Three decode primitives of the SNII index format take numbers read from the file and do arithmetic on them without checking for overflow. - The FRQ prelude added the untrusted `sbdir_len` to the header length before comparing it with the buffer, and summed the super-block lengths into the window region length unchecked. A crafted length wraps the sum to a small value, so the bounds check passes while a Slice of a huge length is cut from a buffer that holds no such bytes, and the block decoder then reads past the end of it. `memory_required` already compared `sbdir_len` with the remaining bytes before calling `verify_covered_crc`, but `open` did not. The overflow check now lives in `verify_covered_crc`, which both call, the super-block sum uses the file's own `checked_add_u64`, and the final region check compares against the room left instead of adding to the start offset. - `decode_varint64` accepted a tenth byte with payload above bit 63. The extra bits were shifted out, and the encoding decoded to a silently truncated value. The check sits on the terminating byte, so the loop over the continuation bytes is unchanged. - `pfor_decode` and `pfor_skip` added each exception index delta to a 32-bit running index and tested the sum afterwards, so a delta could wrap the index back into the block and be accepted. The running index is now 64 bits wide: the index is below the block size before every add and a delta is at most 2^32 - 1, so the sum cannot wrap. Nothing here is reachable from data the writers produce. The checks make a damaged or crafted index file fail with a corruption status instead of being decoded into a wrong value or an out-of-bounds read.
🌍 Read this in other language
English • العربية • বাংলা • Deutsch • Español • فارسی • Français • हिन्दी • Bahasa Indonesia • Italiano • 日本語 • 한국어 • Polski • Português • Română • Русский • Slovenščina • ไทย • Türkçe • Українська • Tiếng Việt • 简体中文 • 繁體中文
?style=for-the-badge){kind=icon}
?style=for-the-badge){kind=icon}
Apache Doris is an open-source, real-time analytics and search database built on MPP architecture. It provides fast SQL analytics, lakehouse query acceleration, and hybrid search across structured, text, and vector data.
Explore the official website for the latest product overview, use cases, ecosystem updates, blogs, and user stories. For version updates, see all release notes.
📈 Use Cases
| Use Case | What it provides |
|---|---|
| Customer-Facing Analytics | Ship sub-second interactive analytics to external users. |
| Data Warehousing | Build one real-time warehouse across business domains. |
| Observability | Analyze high-throughput logs, events, and metrics with SQL. |
| Doris for AI | Use vector, text, JSON, and structured search in one SQL engine. |
🚀 Core Capabilities
Apache Doris is built around three core capabilities. The website is the source of truth for detailed product descriptions and examples.
| Capability | What it provides |
|---|---|
| Real-Time Analytics | Streaming ingestion, incremental transformation, and sub-second queries under high concurrency. |
| Lakehouse Analytics | Fast SQL analytics over open table formats such as Iceberg, Delta Lake, and Hudi. |
| Hybrid Search | SQL-native analytics across JSON, full-text, and vector data for AI and search workloads. |
🔌 Ecosystem
Doris sits at the center of the modern data stack. It connects upstream databases, streaming systems, and lakehouse storage with downstream BI, AI, analytics, and observability tools.
For the latest ecosystem coverage, visit the official website and the connection and integration documentation.
👣 Get Started
🧱 Architecture
Apache Doris supports both compute-storage coupled and compute-storage decoupled deployments. In decoupled mode, stateless compute groups run over shared object storage, so you can scale compute on demand and isolate workloads.
Learn more in the deployment guide and deployment mode guide.
📣 Project Updates
| Resource | What it provides |
|---|---|
| Community Report | Weekly updates on community activity, merged PRs, contributors, and feature progress. |
| Roadmap 2026 | The 2026 planning discussion for AI and hybrid search, query engine, storage, and data lake work. |
🧩 Components
Doris provides connectors and tools for common data engineering workflows.
- Doris Flink Connector
- Doris Spark Connector
- Doris Kafka Connector
- Doris Stream Loader
- Doris Kubernetes Operator
👨👩👧👦 Users
Apache Doris is used in production by thousands of companies worldwide across internet services, finance, retail, logistics, manufacturing, energy, telecommunications, AI, and other industries.
🙌 Contributors
Apache Doris graduated from the Apache Incubator and became an Apache Top-Level Project in June 2022. Thanks to all community contributors who help build Doris.
🌈 Community and Support
💬 Contact Us
🧰 Links
- Apache Doris official website: doris.apache.org
- X: @doris_apache
- Medium: @ApacheDoris
📜 License
Note
Some licenses of the third-party dependencies are not compatible with Apache 2.0 License. So you need to disable some Doris features to comply with Apache 2.0 License. For details, refer to the
thirdparty/LICENSE.txt