From neuvector-updates at lists.suse.com Tue Mar 29 23:00:42 2022 From: neuvector-updates at lists.suse.com (NeuVector Updates for new release and security updates for the NeuVector container security platform) Date: Tue, 29 Mar 2022 23:00:42 +0000 Subject: SUSE NeuVector 5.0 preview3 is now available for testing, + EOL of registry.neuvector.com Message-ID: Hello, You are receiving this email because you are a member of the NeuVector Technical Updates mailing list. To unsubscribe or manage your subscription please go to https://lists.suse.com/mailman/listinfo/neuvector-updates SUSE NeuVector v5.0 (Open Source) preview3 Available for Testing * Preview3 version can be pulled from Docker Hub * Adds SLE vulnerability scanning for run-time (containers, nodes etc). Registry/image scanning already supported in preview2 * Offers first views of new features such as Zero-drift process protection, Split mode protection for Network and Process, WAF rules, CRD for WAF, DLP and Admission Controls, RKE2 support and more! See the preview3 release notes for more details. * The source code on github/neuvector/ has been updated to preview3 accordingly. Reminder: build tools are not yet available but are scheduled to be made available in May. * Documentation at https://open-docs.neuvector.com is in the process of being updated for new features. * The General Availability (GA) of the 5.0 version is currently targeted for May, 2022. NeuVector Private Registry registry.neuvector.com to be EOL October 1, 2022 The NeuVector images are now available on Docker Hub as publicly available and can be pulled without credentials. This includes the latest 4.x (closed source) as well as 5.x (open source) images. It is no longer required to access the NeuVector customer portal at console.cloud.neuvector.com to retrieve credentials in order to pull images. The private registry registry.neuvector.com will be retired on October 1, 2022 and will no longer support image pulls for the NeuVector images. In order to transition to pulling from Docker Hub: * Change image registry to docker.io * Change image paths from ?registry.neuvector.com/? to ?neuvector/? and use appropriate image names and tags. Check image names for manager, controller, enforcer, scanner, updater (or allinone if using) * Remove the regsecret for registry.neuvector.com as login is no longer required. * If needed, allow access to docker.io through corporate firewalls * Update Helm chart to the latest, which supports both options, and make sure registry is docker.io and image paths start with ?neuvector/? * If needed, check any automated scripts that were pulling from registry.neuvector.com and update to docker.io Enterprise customers of NeuVector can contact support at neuvector.com for any questions. Best regards, The SUSE NeuVector team -------------- next part -------------- An HTML attachment was scrubbed... URL: From neuvector-updates at lists.suse.com Wed Mar 30 19:13:07 2022 From: neuvector-updates at lists.suse.com (NeuVector Updates for new release and security updates for the NeuVector container security platform) Date: Wed, 30 Mar 2022 19:13:07 +0000 Subject: [Security Update] NeuVector 4.4.4-s2 addresses OpenSSL Alpine CVE-2022-0778 Message-ID: To the NeuVector Technical Update subscribers, Important: This security update is for the closed source, 4.x version of NeuVector. The open source 5.x (preview) versions will be updated during the next update cycle. A vulnerability in OpenSSL rated as High affects the Alpine image used in the NeuVector Controller, Manager, and Enforcer images. NeuVector version 4.4.4-s2 remediates this CVE and has been published to Docker Hub (public) and registry.neuvector.com (private registry). CVE-2022-0778 - A flaw was found in OpenSSL. It is possible to trigger an infinite loop by crafting a certificate that has invalid elliptic curve parameters. Since certificate parsing happens before verification of the certificate signature, any process that parses an externally supplied certificate may be subject to a denial of service attack. Detailed description: The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc). Informational links: https://security.alpinelinux.org/vuln/CVE-2022-0778 https://www.suse.com/security/cve/CVE-2022-0778.html https://nvd.nist.gov/vuln/detail/CVE-2022-0778 If you believe you are affected by this CVE, please update to the 4.4.4-s2 version of NeuVector. Enterprise customers of NeuVector can contact support at neuvector.com for any questions. Best regards, The NeuVector Team You are receiving this email because you are a member of the NeuVector Technical Updates mailing list. To unsubscribe or manage your subscription please go to https://lists.suse.com/mailman/listinfo/neuvector-updates -------------- next part -------------- An HTML attachment was scrubbed... URL: