Skip to content

Fix handling bad data while reading in Protobuf format.#11258

Merged
alexey-milovidov merged 2 commits intoClickHouse:masterfrom
vitlibar:protobuf-fix-handling-bad-data
May 28, 2020
Merged

Fix handling bad data while reading in Protobuf format.#11258
alexey-milovidov merged 2 commits intoClickHouse:masterfrom
vitlibar:protobuf-fix-handling-bad-data

Conversation

@vitlibar
Copy link
Copy Markdown
Member

@vitlibar vitlibar commented May 28, 2020

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Changelog category:

  • Bug Fix

Changelog entry:
Fix crash while reading malformed data in Protobuf format.
This fixes #5957, fixes #11203.

@blinkov blinkov added the pr-bugfix Pull request with bugfix, not backported by default label May 28, 2020
@vitlibar vitlibar force-pushed the protobuf-fix-handling-bad-data branch from 771b90b to a452d03 Compare May 28, 2020 15:41
@alexey-milovidov alexey-milovidov self-assigned this May 28, 2020
@alexey-milovidov alexey-milovidov merged commit fb4d272 into ClickHouse:master May 28, 2020
KochetovNicolai pushed a commit that referenced this pull request Jun 8, 2020
Fix handling bad data while reading in Protobuf format.

(cherry picked from commit fb4d272)
KochetovNicolai pushed a commit that referenced this pull request Jun 8, 2020
Fix handling bad data while reading in Protobuf format.

(cherry picked from commit fb4d272)
KochetovNicolai pushed a commit that referenced this pull request Jun 8, 2020
Fix handling bad data while reading in Protobuf format.

(cherry picked from commit fb4d272)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-docs-needed pr-bugfix Pull request with bugfix, not backported by default

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Malformed Protobuf file can lead to server crash Crash with Kafka engine (format Protobuf) when sending unexpected messages

5 participants