CVE Kimliği: CVE-2022-31231
Önem Derecesi: Orta
Dell, xDoctor'u yükseltmek ve yamayı yüklemek için Müşteriden bu prosedürü gerçekleştirmesini talep eder. Bu, söz konusu güvenlik açığına uzun süre maruz kalmayı önlemek için en hızlı ve en güvenli yöntemdir. Tüm adımlar bu makalede ayrıntılı olarak açıklanmıştır. Aşağıdaki bağlantıdan erişilen bu makaleye eşlik etmesi için izlenebilecek bir video kılavuzu da bulunmaktadır.
Şu durumlarda olası G/Ç zaman aşımlarını bekleyin: dataheadsvc services
düğüm düğüm yeniden başlatılır. Uygulamaların kümeye bir yük dengeleyici üzerinden erişmesi ve G/Ç zaman aşımını işleyebilmesi gerekir. Bu prosedür gerçekleştirilirken bir bakım aralığı önerilir.
Aşağıda gösterildiği gibi bir ECS üzerindeki tüm kovalar yalnızca CAS ise bu güvenlik açığı ECS'yi etkilemiyordur. Düzeltme ekini uygulamak gerekli değildir ve bu makaleye uyulması zorunlu değildir.
Komut:
# svc_bucket list
Example:
admin@ecs-n1:~> svc_bucket list svc_bucket v1.0.33 (svc_tools v2.5.1) Started 2022-07-08 08:49:11 Bucket Temp Replication Owner Owner API FS Versioning Failed Bucket Name Namespace Group User VDC Type Enabled Enabled (TSO) cas_bucket region_ns RG1 casuser VDC1 CAS false Disabled False cas_bu region_ns RG1 cas_obj VDC1 CAS false Disabled False test region_ns RG1 test1 VDC1 CAS false Disabled False test_cas region_ns RG1 test_cas VDC1 CAS false Disabled False test_bkt_cas region_ns RG1 user_test VDC1 CAS false Disabled False Friday_cas region_ns RG1 Friday_cas VDC1 CAS false Disabled False
Hizmet yeniden başlatmaları arasında düğüm başına 60 saniyelik bir gecikme varsayılan olarak ayarlanır. Sanal Veri Merkezi'ndeki (VDC) düğüm sayısı, gereken hazırlık, hizmet stabilizasyonu ve son kontroller için 60 saniye + 30 dakika ile çarpılır.
Örnekler:
48 düğümlü bir VDC ECS yaklaşık 80 dakika sürebilir:
60 saniye X 48 (VDC düğümü sayısı) + 30 dakika (hazırlık) = yaklaşık 80 dakika.
Sekiz düğümlü bir VDC ECS işlemi yaklaşık 40 dakika sürebilir:
60 saniye X 8 (VDC düğümü sayısı) + 30 dakika (hazırlık) = yaklaşık 40 dakika
S: Yama, xDoctor sürümünün bir parçası mı?
C: Yama yükleme komut dosyası, xDoctor sürüm 4.8-84 ve katmanının bir parçasıdır. xDoctor'ı indirme ve yama yükleme işleminin yürütülmesine yönelik talimatlar çözüm adımlarında yer almaktadır.
S: Birden fazla VDC'yi paralel olarak güncelleştirebilir miyim?
C: Hayır, tek seferde yalnızca bir VDC'yi güncelleştirebilirsiniz.
Soru: Bu prosedürü çalıştırdıktan sonra ECS'yi yükseltirsem yükseltme sonrasında prosedürü yeniden çalıştıracak mıyım?
C: DSA-2022-153'te belirtilip kalıcı düzeltmeye sahip olan kod sürümüne yükseltme yapıyorsanız hayır. Evet, aynı DSA'da belirtilmeyen bir kod sürümüne yükseltme yapıyorsanız.
Soru: Düğüm değişimi, yeniden görüntü oluşturma veya genişletme işlemlerinden sonra daha önce yüklendiği ECS'de düzeltme ekinin yeniden uygulanması gerekir mi?
Cevap: VDC, DSA-2022-153'te belirtilip kalıcı düzeltmeye sahip olan kod sürümündeyse hayır. Evet, aynı DSA'da belirtilmeyen bir kod sürümü çalıştıran bir VDC'ye karşı bu eylemlerden herhangi birini yapıyorsanız. Bu senaryolar için yama gerektiğinde söz konusu Dell mühendisi iletişime geçerek güncellemenin gerekli olduğunu bildirir.
Soru: IAM kullanmıyor ve yalnızca eski kullanıcıları kullanıyorsam ne olur?
Cevap: Müşteriler, IAM yerine yalnızca eski kullanıcılar kullanılıyorsa yamayı uygulamalıdır.
Soru: Bu KB deki tüm komutları çalıştırmak için hangi kullanıcıda oturum açmalıyız?
A: yönetici
S: Yapar svc_patch
tüm raflarda veya bir VDC'de birden fazla rafın olduğu özel bir MACHINES dosyasıyla çalıştırılması gerekiyor mu?
Cevap: Hayır, birden fazla raf olup olmadığını otomatik olarak algılar ve bu VDC'deki tüm raflardaki tüm düğümleri günceller.
Soru: Hedef xDoctor sürümünün artık 4.8-84.0 olmadığını fark ettim. Neden?
C: xDoctor sürümleri sık sık meydana gelir, bu nedenle her zaman yayınlanan en yüksek sürüme yükseltmeniz önerilir. Düzeltmeyi daha önce 4.8-84.0 kullanarak çalıştırdıysak ECS, güvenlik açığına karşı tamamen korunur ve yeniden çalıştırılması gerekmez.
svc_patch
xDoctor ile birlikte gelen araç.ECS xDoctor yazılımınızı mevcut en son sürüme yükseltin.
# sudo xdoctor --version
admin@node1:~> sudo xdoctor --version 4.8-84.0
# sudo xdoctor --upgrade --local=/home/admin/xDoctor4ECS-4.8-84.0.noarch.rpm
admin@ecs-n1:~> sudo xdoctor --upgrade --local=/home/admin/xDoctor4ECS-4.8-84.0.noarch.rpm 2022-07-04 07:41:49,209: xDoctor_4.8-83.0 - INFO : xDoctor Upgrader Instance (1:SFTP_ONLY) 2022-07-04 07:41:49,210: xDoctor_4.8-83.0 - INFO : Local Upgrade (/home/admin/xDoctor4ECS-4.8-84.0.noarch.rpm) 2022-07-04 07:41:49,226: xDoctor_4.8-83.0 - INFO : Current Installed xDoctor version is 4.8-83.0 2022-07-04 07:41:49,242: xDoctor_4.8-83.0 - INFO : Requested package version is 4.8-84.0 2022-07-04 07:41:49,242: xDoctor_4.8-83.0 - INFO : Updating xDoctor RPM Package (RPM) 2022-07-04 07:41:49,293: xDoctor_4.8-83.0 - INFO : - Distribute package 2022-07-04 07:41:50,759: xDoctor_4.8-83.0 - INFO : - Install new rpm package 2022-07-04 07:42:04,401: xDoctor_4.8-83.0 - INFO : xDoctor successfully updated to version 4.8-84.0
# svc_exec -m "ip address show private.4 |grep -w inet"
admin@ecsnode1~> svc_exec -m "ip address show private.4 |grep -w inet" svc_exec v1.0.2 (svc_tools v2.1.0) Started 2021-12-20 14:03:33 Output from node: r1n1 retval: 0 inet 169.254.1.1/16 brd 169.254.255.255 scope global private.4 Output from node: r2n1 retval: 0 inet 169.254.2.1/16 brd 169.254.255.255 scope global private.4 Output from node: r3n1 retval: 0 inet 169.254.3.1/16 brd 169.254.255.255 scope global private.4 Output from node: r4n1 retval: 0 inet 169.254.4.1/16 brd 169.254.255.255 scope global private.4
admin@ecs-n1: scp xDoctor4ECS-4.8-84.0.noarch.rpm 169.254.2.1:/home/admin/ xDoctor4ECS-4.8-84.0.noarch.rpm 100% 32MB 31.9MB/s 00:00 admin@ecsnode1~> scp xDoctor4ECS-4.8-84.0.noarch.rpm 169.254.3.1:/home/admin/ xDoctor4ECS-4.8-84.0.noarch.rpm 100% 32MB 31.9MB/s 00:00 admin@ecsnode1~> scp xDoctor4ECS-4.8-784.0.noarch.rpm 169.254.4.1:/home/admin/ xDoctor4ECS-4.8-84.0.noarch.rpm 100% 32MB 31.9MB/s 00:00 admin@ecsnode1~>
# sudo xdoctor --upgrade --local=/home/admin/xDoctor4ECS-4.8-84.0.noarch.rpm
# svc_dt check -b
admin@ecs-n1: svc_dt check -b svc_dt v1.0.27 (svc_tools v2.4.1) Started 2022-06-14 11:34:26 Date Total DT Unknown # Unready # RIS Fail # Dump Fail # Check type Time since check Check successful 2022-06-14 11:34:09 1920 0 0 0 0 AutoCheck 0m 17s True 2022-06-14 11:32:59 1920 0 0 0 0 AutoCheck 1m 27s True 2022-06-14 11:31:48 1920 0 0 0 0 AutoCheck 2m 38s True 2022-06-14 11:30:38 1920 0 0 0 0 AutoCheck 3m 48s True 2022-06-14 11:29:28 1920 0 0 0 0 AutoCheck 4m 58s True 2022-06-14 11:28:18 1920 0 0 0 0 AutoCheck 6m 8s True 2022-06-14 11:27:07 1920 0 0 0 0 AutoCheck 7m 19s True 2022-06-14 11:25:57 1920 0 0 0 0 AutoCheck 8m 29s True 2022-06-14 11:24:47 1920 0 0 0 0 AutoCheck 9m 39s True 2022-06-14 11:23:37 1920 0 0 0 0 AutoCheck 10m 49s True
# /opt/emc/xdoctor/patches/CVE-2022-31231_iam-fix/svc_patch status
admin@ecs-n1:~> /opt/emc/xdoctor/patches/CVE-2022-31231_iam-fix/svc_patch status svc_patch Version 2.9.2 Verifying patch bundle consistency DONE Detecting nodes in current VDC DONE Reading in patch details (1 of 2) DONE Reading in patch details (2 of 2) DONE Validating nodes are online DONE Checking Installed Patches and Dependencies DONE Patches/releases currently installed: n/a (Base release) Patches that need to be installed: CVE-2022-31231_iam-fix (PatchID: 3525) Files that need to be installed: /opt/storageos/conf/iam.object.properties (from CVE-2022-31231_iam-fix) /opt/storageos/lib/storageos-iam.jar (from CVE-2022-31231_iam-fix) The following services need to be restarted: dataheadsvc
# screen -S patchinstall # unset TMOUT # /opt/emc/xdoctor/patches/CVE-2022-31231_iam-fix/svc_patch install
admin@ecs-n1:~> screen -S patchinstall admin@ecs-n1:~> unset TMOUT admin@ecs-n1:~> /opt/emc/xdoctor/patches/CVE-2022-31231_iam-fix/svc_patch install svc_patch Version 2.9.2 Verifying patch bundle consistency DONE Detecting nodes in current VDC DONE Reading in patch details (1 of 2) DONE Reading in patch details (2 of 2) DONE Validating nodes are online DONE Checking Installed Patches and Dependencies DONE Patches/releases currently installed: n/a (Base release) Patches that will be installed: CVE-2022-31231_iam-fix (PatchID: 3525) Files that will be installed: /opt/storageos/conf/iam.object.properties (from CVE-2022-31231_iam-fix) /opt/storageos/lib/storageos-iam.jar (from CVE-2022-31231_iam-fix) The following services will be restarted: dataheadsvc Patch Type: Standalone Number of nodes: 5 Number of seconds to wait between restarting node services: 60 Check DT status between node service restarts: false Do you wish to continue (y/n)?y Distributing files to node 169.254.1.1 Distributing patch installer to node '169.254.1.1' Distributing files to node 169.254.1.2 Distributing patch installer to node '169.254.1.2' Distributing files to node 169.254.1.3 Distributing patch installer to node '169.254.1.3' Distributing files to node 169.254.1.4 Distributing patch installer to node '169.254.1.4' Distributing files to node 169.254.1.5 Distributing patch installer to node '169.254.1.5' Restarting services on 169.254.1.1 Restarting dataheadsvc Waiting 60 seconds for services to stabilize...DONE Restarting services on 169.254.1.2 Restarting dataheadsvc Waiting 60 seconds for services to stabilize...DONE Restarting services on 169.254.1.3 Restarting dataheadsvc Waiting 60 seconds for services to stabilize...DONE Restarting services on 169.254.1.4 Restarting dataheadsvc Waiting 60 seconds for services to stabilize...DONE Restarting services on 169.254.1.5 Restarting dataheadsvc Waiting 60 seconds for services to stabilize...DONE Patching complete.
admin@node1:/> exit logout [screen is terminating] admin@node1:/>
admin@node 1:~> screen -ls There is a screen on: 113275.pts-0.ecs-n3 (Detached) 1 Socket in /var/run/uscreens/S-admin.
admin@node1:~> screen -r 113277.pts-0.ecs-n3
# /opt/emc/xdoctor/patches/CVE-2022-31231_iam-fix/svc_patch status
admin@ecs-n1:~> /opt/emc/xdoctor/patches/CVE-2022-31231_iam-fix/svc_patch status svc_patch Version 2.9.2 Verifying patch bundle consistency DONE Detecting nodes in current VDC DONE Reading in patch details (1 of 2) DONE Reading in patch details (2 of 2) DONE Validating nodes are online DONE Checking Installed Patches and Dependencies DONE Patches/releases currently installed: CVE-2022-31231_iam-fix (PatchID: 3525) Fix for ECS iam vulnerability CVE-2022-31231 n/a (Base release) Patches that need to be installed: No files need to be installed. The following services need to be restarted: No services need to be restarted.
admin@ecs-n1:~> /opt/emc/xdoctor/patches/CVE-2022-31231_iam-fix/svc_patch status svc_patch Version 2.9.2 Verifying patch bundle consistency DONE Detecting nodes in current VDC DONE Reading in patch details (1 of 2) DONE Reading in patch details (2 of 2) DONE Validating nodes are online DONE Checking Installed Patches and Dependencies DONE Patches/releases currently installed: n/a (Base release) Patches that need to be installed: CVE-2022-31231_iam-fix (PatchID: 3525) Files that need to be installed: /opt/storageos/conf/iam.object.properties (from CVE-2022-31231_iam-fix) /opt/storageos/lib/storageos-iam.jar (from CVE-2022-31231_iam-fix) The following services need to be restarted: dataheadsvc
admin@ecs-n1 /opt/emc/xdoctor/patches/CVE-2022-31231_iam-fix/svc_patch status svc_patch Version 2.9.2 Verifying patch bundle consistency DONE Detecting nodes in current VDC DONE Reading in patch details (1 of 2) DONE Reading in patch details (2 of 2) DONE Validating nodes are online DONE Checking Installed Patches and Dependencies FAILED Fatal: Currently installed version of storageos-iam.jar is unknown. This likely means that a custom Isolated Patch is installed. Please contact your next level of support for further steps, and include this information Detected md5sum: 6ec26421d426365ecb2a63d8e0f8ee4f
svc_patch Version 2.9.2 Verifying patch bundle consistency DONE Detecting nodes in current VDC DONE Reading in patch details (1 of 2) DONE Reading in patch details (2 of 2) DONE Validating nodes are online FAILED ERROR: Could not execute commands on the object-main container on 169.254.x.x Output was 'Failed to add the host to the list of known hosts (/home/admin/.ssh/known_hosts). :patchtest:' Patching is unable to continue with unreachable nodes. To proceed: - Resolve problems accessing node(s) from this one. - Manually pass a MACHINES file containing the list of working nodes to patch (not recommended). - Contact your next level of support for other options or assistance.
/home/admin/.ssh/known_hosts
varsayılan olarak yönetici olması gereken köktü.
admin@node1:~> ls -l /home/admin/.ssh/known_hosts -rw------- 1 root root 1802 Jul 23 2019 /home/admin/.ssh/known_hosts admin@ecs:~>
# sudo chown admin:users /home/admin/.ssh/known_hosts
admin@node1:~> sudo chown admin:users /home/admin/.ssh/known_hosts
admin@node1:~> /opt/emc/xdoctor/patches/CVE-2022-31231_iam-fix/svc_patch install
/home/admin/.ssh/known_hosts
.svc_patch Version 2.9.2 Verifying patch bundle consistency DONE Detecting nodes in current VDC DONE Reading in patch details (1 of 2) DONE Reading in patch details (2 of 2) DONE Validating nodes are online FAILED ERROR: Could not execute commands on the object-main container on 169.254.x.x Output was '@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is SHA256:RcwOsFj7zPA5p5kSeYovF4UlZTm125nLVeCL1zCqOzc. Please contact your system administrator. Add correct host key in /home/admin/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /home/admin/.ssh/known_hosts:14 You can use following command to remove the offending key: ssh-keygen -R 169.254.x.x -f /home/admin/.ssh/known_hosts Password authentication is disabled to avoid man-in-the-middle attacks. Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks. :patchtest:' Patching is unable to continue with unreachable nodes. To proceed: - Resolve problems accessing node(s) from this one. - Manually pass a MACHINES file containing the list of working nodes to patch (not recommended). - Contact your next level of support for other options or assistance.
# /opt/emc/xdoctor/patches/CVE-2022-31231_iam-fix/svc_patch status svc_patch Version 2.9.3 Verifying patch bundle consistency FAILED Patch bundle consistency check failed - md5sums for one or more files in the patch bundle were invalid, or files were not found. svc_patch will attempt to validate files in the patch using MD5SUMS.bundle, which is bundled with the patch. Output from md5sum was: ./lib/libs/svc_base.py: FAILED md5sum: WARNING: 1 computed checksum did NOT match
# sudo sed -i '/svc_base.py/d' /opt/emc/xdoctor/patches/CVE-2022-31231_iam-fix/MD5SUMS.bundle # sudo sed -i '/MD5SUMS.bundle/d' /opt/emc/xdoctor/.xdr_chksum