Return-Path: X-Original-To: apmail-kafka-dev-archive@www.apache.org Delivered-To: apmail-kafka-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D9B5B18BFC for ; Fri, 29 Jan 2016 13:17:46 +0000 (UTC) Received: (qmail 60107 invoked by uid 500); 29 Jan 2016 13:17:40 -0000 Delivered-To: apmail-kafka-dev-archive@kafka.apache.org Received: (qmail 59959 invoked by uid 500); 29 Jan 2016 13:17:40 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 59874 invoked by uid 99); 29 Jan 2016 13:17:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jan 2016 13:17:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id DC4362C1F5D for ; Fri, 29 Jan 2016 13:17:39 +0000 (UTC) Date: Fri, 29 Jan 2016 13:17:39 +0000 (UTC) From: "Rajini Sivaram (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KAFKA-3169) Kafka broker throws OutOfMemory error with invalid SASL packet MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KAFKA-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-3169: ---------------------------------- Status: Patch Available (was: Open) > Kafka broker throws OutOfMemory error with invalid SASL packet > -------------------------------------------------------------- > > Key: KAFKA-3169 > URL: https://issues.apache.org/jira/browse/KAFKA-3169 > Project: Kafka > Issue Type: Bug > Components: security > Affects Versions: 0.9.0.0 > Reporter: Rajini Sivaram > Assignee: Rajini Sivaram > Priority: Critical > Fix For: 0.9.0.1 > > > Receive buffer used in Kafka servers to process SASL packets is unbounded. This can results in brokers crashing with OutOfMemory error when an invalid SASL packet is received. > There is a standard SASL property in Java _javax.security.sasl.maxbuffer_ that can be used to specify buffer size. When properties are added to the Sasl implementation in KAFKA-3149, we can use the standard property to limit receive buffer size. > But since this is a potential DoS issue, we should set a reasonable limit in 0.9.0.1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)