From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id C926E3858D34 for ; Thu, 2 May 2024 10:35:56 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C926E3858D34 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org C926E3858D34 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.133.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1714646161; cv=none; b=D46RNMjmkZiCrgX0kt4snpnityHpgMAjulUmNbujirI7KTAtKZsy2RoQ5c8IfVtAzxuqrFajGRQV6xsLQi73N33d1MKCJirdP3mPH/d29GO/CjKhs1YyK+oByGL6ZiOvrtfx2jJueFT0u2w8G92tqeNYrzMy6x/tWyLUqEmdZAs= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1714646161; c=relaxed/simple; bh=Z7vGvySEdcdJhSeuxem//x85HD/x1g2kvczNSioGa5c=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=uvUbHTYXZc1mgOUfb7x4X2rHw5Uhy69prj9WdpACj/aQXacxnmgBc4RLi8r5KskaRB4nGLKyZGBHhNmP9PdT9c4a737nyrh9elb9+pAJr7hnbLNfTCgl/ftY8eqHZCV7hUt56zoXxIkDF7P1zDEVUT/yw+E9SG7OEfoGllrbdU0= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1714646156; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=h9LZRVUoPSCNGiUSgZxOoIUt2A/NNZ2qAdBMDqwS0Rc=; b=PyIPKADkQD6avNuO0Ho3KaTrYN3eetzm09WxQi6rnm6M130oeWf4YXSX20qaPLBaYhN/lS c0vbIItP8uLC8KdapHoophdRR5U0kkbyYxz0JavPhY+CN98aI5n3WqfBHoqhMtVd6Sx2Eq +h8bCA0G7msLHc+RpF+4vDxB4p4dlvo= Received: from mail-qt1-f198.google.com (mail-qt1-f198.google.com [209.85.160.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-528-wC0-sk3DOi6tltkMQ3GkQQ-1; Thu, 02 May 2024 06:35:54 -0400 X-MC-Unique: wC0-sk3DOi6tltkMQ3GkQQ-1 Received: by mail-qt1-f198.google.com with SMTP id d75a77b69052e-4396bacb290so104003961cf.3 for ; Thu, 02 May 2024 03:35:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714646154; x=1715250954; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=h9LZRVUoPSCNGiUSgZxOoIUt2A/NNZ2qAdBMDqwS0Rc=; b=vyuZB4wO+v3vu/8LLixQimH6IifarowGAvXHPMXmZ18jzzhwAG0HrKHIbeqQkCc9/P j8IrekgjkneZbRMQ0IBRtcZMedWzY/HJ69RI2IqJ6sxcmZXPqO/BvPR9Zn9LiclGMBru DnloBNylGPxPJbu/W3C+cC/pufyqDyNKJiv7bAqGWx9tdfwzyfA1kKd8kgyGorJHUKYo yCvY1yf+5jJIO/ib/Je0FpKMslokTQfLo6JmVMNJKV6g9IfNcG4/2MGM22aevBEW8Pcd /19vhStwhhICc2jVIsvxDkjJ40uzPQe1SEI9g9oOEX0xDSSFuPxgKfi+qhu/bs17gjI5 x0bw== X-Forwarded-Encrypted: i=1; AJvYcCXuvzN80NxkTUmTeBQNXyPuZEDv3j7BfSx7v9AmaDActh3w6Nuxze3PAwD+MxcIzhGVz/FyIvYTDA5I31mqPjohlI2wQAUP9nQ9 X-Gm-Message-State: AOJu0Yx3YVGEz+39mIZAO96160RIrzEQNAGyx2jsbA+B01lxCUJZqNyf 514ERiWfT9KatGT7v2FoMfiZ195B7u2e5ooVfFL9NuGKSRd8IYHVT64FYafJ4oA4s1uEpjpqXQP oTiiFHqF1K3yG0LeG3/EDcBC5y4tSUov4ghSdOJq/jqwvr+OnNRA95TxOiA== X-Received: by 2002:a05:622a:189a:b0:43c:60f8:2f9d with SMTP id v26-20020a05622a189a00b0043c60f82f9dmr6856394qtc.43.1714646153922; Thu, 02 May 2024 03:35:53 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFwILEW4GlH2RCZue+HXBhuDGNf8qBGc64SI4J8+6cNWUnn65yHUNOrT19pv+lfU5DonzDflg== X-Received: by 2002:a05:622a:189a:b0:43c:60f8:2f9d with SMTP id v26-20020a05622a189a00b0043c60f82f9dmr6856376qtc.43.1714646153514; Thu, 02 May 2024 03:35:53 -0700 (PDT) Received: from [192.168.0.182] ([142.198.113.116]) by smtp.gmail.com with ESMTPSA id bt9-20020ac86909000000b00437a02f67c5sm344376qtb.49.2024.05.02.03.35.52 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 02 May 2024 03:35:53 -0700 (PDT) Message-ID: Date: Thu, 2 May 2024 06:35:44 -0400 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: What is our SLA for going from reserved CVE to published CVE? To: Carlos O'Donell , libc-alpha , Adhemerval Zanella References: From: Siddhesh Poyarekar In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-15.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,RCVD_IN_SORBS_WEB,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 2024-05-01 22:12, Carlos O'Donell wrote: > Raising this on libc-alpha for a broader discussion. > > For CVE-2024-33599, CVE-2024-33600, CVE-2024-33601 and CVE-2024-33602 > the glibc security team has not yet published the CVE IDs, only reserved > the block. > > I have just completed filling in the advisories and have all the data > for publishing them along with publishing the CVE IDs [1]. > > I could have published the CVE IDs *earlier* but my reading of the CNA > rules is that: > ~~~ > 2.2.3 SHOULD provide the CVE Record information within 24 hours of > publishing the CVE ID. > ~~~ > > So once I publish the CVE ID I need to move quickly to fill in all the > record information... which I don't have until I complete the > advisory text. > > For these CVE IDs it will have been ~7-8 days to publish, which is too > long IMO, but we can improve that. > > Under embargo was certainly easier because the timeline gives us time > to write the advisory text and get it ready for publishing. > > Would it be better if we just published interm text and updated as we go? The CVE record tends to have a single line description that identifies affected functionality and versions, which I think we should be able to deliver when we reserve the CVE. One thing I haven't tested yet is the feature to publish records at a specific future date. If that works, we could make it part of our workflow to add a description at the time of CVE number reservation, regardless of embargo state. Thanks, Sid