اسپلانک در بولتن امنیتیش برای یک ژوئن ، 11 خرداد، چندین آسیب پذیری رو در محصولات مختلفش اصلاح کرده. بخشی از این بروزرسانی برای اصلاح آسیب پذیری ها در برنامه های شخص ثالثی هستش که محصولات اسپلانک ازشون استفاده میکنه و بقیه که 13 مورد هستش برای خود محصولات اسپلانک هست. از این 12 مورد ، 5 موردش با شدت بالا، 6 موردش با شدت متوسط و یه موردش با شدت پایین هستش که در این پست به بررسی آسیب پذیری های با شدت بالا پرداختیم.
آسیب پذیری CVE-2023-32706 :
آسیب پذیری از نوع DoS هستش و شدت بالا و امتیاز 7.7 داره. مهاجم بدون احراز هویت با ارسال پیام های مخرب (XML Tag) به تجزیه کننده XML ،درون SAML authentication منجر به DoS در Splunk daemon میشه. آسیب پذیری زمانی اتفاق می افته که ، تجزیه کننده XML که پیکربندی نادرستی داره، یه ورودی XML حاوی ارجاع به یه موجودیت گسترده (entity expansion) دریافت میکنه و باعث میشه تجزیه کننده XML از تمام مموری دستگاه استفاده کنه و باعث کرش Splunk daemon یا خاتمه اون توسط سیستم عامل بشه.
نسخه های تحت تاثیر و اصلاح شده:
| محصول | نسخه | مولفه | نسخه تحت تاثیر |
نسخه اصلاح شده |
|---|---|---|---|---|
| Splunk Enterprise | 8.1 | Splunk Web | 8.1.0 to 8.1.13 | 8.1.14 |
| Splunk Enterprise | 8.2 | Splunk Web | 8.2.0 to 8.2.10 | 8.2.11 |
| Splunk Enterprise | 9.0 | Splunk Web | 9.0.0 to 9.0.4 | 9.0.5 |
| Splunk Cloud Platform | 9.0.2303 and below | Splunk Web | 9.0.2303.100 |
اگه نتونید بروزرسانی رو اعمال کنید، باید SAML SSO رو غیرفعال کنید.
آسیب پذیری CVE-2023-32707 :
آسیب پذیری از نوع افزایش امتیاز و امتیاز 8.8 داره و آسیب پذیری با بیشترین امتیاز در این بروزسانی داره. یه کاربر با امتیاز پایین که دارای رولی با قابلیت edit_user هستش، میتونه با ارسال درخواست مخرب، امتیازش به کاربر ادمین ارتقاء بده.آسیب پذیری به این دلیله که قابلیت edit_user از تنطیمات grantableRoles در فایل پیکربندی authorize.conf تبعیت نمیکنه.
برای اینکه بدونید این قابلیت رو به کی دادید، از این راهنما استفاده کنید .
نسخه های تحت تاثیر و اصلاح شده:
| محصول | نسخه | مولفه | نسخه تخت تاثیر |
نسخه اصلاح شده |
|---|---|---|---|---|
| Splunk Enterprise | 8.1 | Splunk Web | 8.1.0 to 8.1.13 | 8.1.14 |
| Splunk Enterprise | 8.2 | Splunk Web | 8.2.0 to 8.2.10 | 8.2.11 |
| Splunk Enterprise | 9.0 | Splunk Web | 9.0.0 to 9.0.4 | 9.0.5 |
| Splunk Cloud Platform | 9.0.2303 and below | Splunk Web | 9.0.2303.100 |
آسیب پذیری CVE-2023-32708:
یه کاربر با امتیاز پایین ، میتونه آسیب پذیری HTTP response splitting رو از طریق دستور rest در SPL داشته باشه که امکان دسترسی به سایر نقاط پایانی REST رو میده. دلیل آسیب پذیری هم اینه که مهاجم میتونه دستور rest رو به پارامتر q در درخواست GET تزریق کنه. برای اکسپلویت نیاز هستش که کاربر هدف فریب بده تا در مرورگرش درخواست اجرا کنه. آسیب پذیری شدت بالا و امتیاز 7.2 داره.
نسخه های تحت تاثیر و اصلاح شده:
| محصول | نسخه | مولفه | نسخه تخت تاثیر |
نسخه اصلاح شده |
|---|---|---|---|---|
| Splunk Enterprise | 8.1 | Splunk Web | 8.1.0 to 8.1.13 | 8.1.14 |
| Splunk Enterprise | 8.2 | Splunk Web | 8.2.0 to 8.2.10 | 8.2.11 |
| Splunk Enterprise | 9.0 | Splunk Web | 9.0.0 to 9.0.4 | 9.0.5 |
| Splunk Cloud Platform | 9.0.2303 and below | Splunk Web | 9.0.2303.100 |
اگه بروزرسانی نتونستید اعمال کنید میتونید در Splunk Enterprise، با ویرایس فایل limits.conf و دادن مقدار 0 یا 1 به max_searches_per_process ، تعداد جستجوهایی که یه پروسس میتونه انجام بده رو محدود کنید.
با استفاده از این راهنما هم میتونید ، HTTP response splitting در نسخه های تحت تاثیر Splunk Enterprise شناسایی کنید.
آسیب پذیری CVE-2023-32713 :
یه کاربر با امتیاز پایین ، میتونه از این آسیب پذیری که در پروسس streamfwd در Splunk App for Stream هستش برای افزایش امتیاز تا کاربر root استفاده کنه. آسیب پذیری شدت بالا و امتیاز 7.8 داره.
نسخه های تحت تاثیر و اصلاح شده:
| محصول | نسخه | مولفه | نسخه تحت تاثیر |
نسخه اصلاح شده |
|---|---|---|---|---|
| Splunk App for Stream | 8.1 | streamfwd | 8.1 and lower | 8.1.1 |
اگه نمیتونید بروزرسانی رو اعمال کنید، یکی از کارهای زیر باید انجام بدید:
- اگه به Splunk App for Stream نیازی ندارید اونو غیر فعال کنیدش.
- Splunk App for Stream رو بعنوان یه کاربر با امتیاز بالا نصب کنید، مثلا کاربری که به فایل
/etc/sudoersاضافه شده. - دسترسی همه کاربران، به غیر از کاربران با امتیاز بالا رو به streamfwd محدود کنید
آسیب پذیری CVE-2023-32714 :
آسیب پذیری از نوع Path Traversal و در Splunk App for Lookup File Editing هستش . شدت بالا و امتیاز 8.1 داره. کاربر با امتیاز پایین که دسترسی به Splunk App for Lookup File Editing داره، میتونه با ارسال یه درخواست وب مخرب این آسیب پذیری رو اکسپلویت کنه و در محدوده دایرکتوری نصب اسپلانک، بخونه و بنویسه.
نسخه های آسیب پذیر و اصلاح شده:
| محصول | نسخه | مولفه | نسخه تحت تاثیر |
نسخه اصلاح شده |
|---|---|---|---|---|
| Splunk App for Lookup File Editing | 4.0 | 4.0 and lower | 4.0.1 |
برای شناسایی این آسیب پذیری در اسپلانک میتونید از این راهنما استفاده کنید.
آسیب پذیری برای برنامه های شخص ثالث در Splunk Enterprise برای ژوئن :
اسپلانک آسیب پذیری های زیر رو در نسخه های 8.1.14, 8.2.11, 9.0.5 و بالاتر اصلاح کرده :
| CVE | Package | Remediation | Severity |
|---|---|---|---|
| CVE-2022-40303 | libxml2 | Patched | High |
| CVE-2022-40304 | libxml2 | Patched | High |
| CVE-2023-0286 | OpenSSL 1.0.2 | Upgraded to 1.0.2zg | High |
| CVE-2023-0215 | OpenSSL 1.0.2 | Upgraded to 1.0.2zg | High |
| CVE-2022-4304 | OpenSSL 1.0.2 | Upgraded to 1.0.2zg | Medium |
| CVE-2023-27538 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2023-27537 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2023-27536 | curl | Upgraded to 8.0.1 | Critical |
| CVE-2023-27535 | curl | Upgraded to 8.0.1 | High |
| CVE-2023-27534 | curl | Upgraded to 8.0.1 | High |
| CVE-2023-27533 | curl | Upgraded to 8.0.1 | High |
| CVE-2023-23916 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2023-23915 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2023-23914 | curl | Upgraded to 8.0.1 | Critical |
| CVE-2022-43552 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-43551 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-42916 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-42915 | curl | Upgraded to 8.0.1 | Critical |
| CVE-2022-35260 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-32221 | curl | Upgraded to 8.0.1 | Critical |
| CVE-2022-35252 | curl | Upgraded to 8.0.1 | Low |
| CVE-2022-32208 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-32207 | curl | Upgraded to 8.0.1 | Critical |
| CVE-2022-32206 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-32205 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-30115 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-27782 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-27781 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-27780 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-27779 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-27778 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-27776 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-27775 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-27774 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-22576 | curl | Upgraded to 8.0.1 | High |
| CVE-2021-22947 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2021-22946 | curl | Upgraded to 8.0.1 | High |
| CVE-2021-22945 | curl | Upgraded to 8.0.1 | Critical |
| CVE-2021-22926 | curl | Upgraded to 8.0.1 | High |
| CVE-2021-22925 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2021-22924 | curl | Upgraded to 8.0.1 | Low |
| CVE-2021-22923 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2021-22922 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2021-22901 | curl | Upgraded to 8.0.1 | High |
| CVE-2021-22898 | curl | Upgraded to 8.0.1 | Low |
| CVE-2021-22897 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2021-22890 | curl | Upgraded to 8.0.1 | Low |
| CVE-2021-22876 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2020-8286 | curl | Upgraded to 8.0.1 | High |
| CVE-2020-8285 | curl | Upgraded to 8.0.1 | High |
| CVE-2020-8284 | curl | Upgraded to 8.0.1 | Low |
| CVE-2020-8231 | curl | Upgraded to 8.0.1 | High |
| CVE-2020-8177 | curl | Upgraded to 8.0.1 | High |
| CVE-2020-8169 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-36227 | libarchive | Upgraded to 3.6.2 | Critical |
| CVE-2021-31566 | libarchive | Upgraded to 3.6.2 | High |
| CVE-2021-36976 | libarchive | Upgraded to 3.6.2 | Medium |
| CVE-2021-3520 | lz4 | Upgraded to 1.9.4 | Critical |
| CVE-2022-35737 | SQLite | Upgraded to 3.41.2 | High |
| CVE-2018-25032 | zlib | Applied patch | High |
| CVE-2022-37434 | zlib | Applied patch | Critical |
| CVE-2020-15138 | prismjs | Upgraded to 1.2.9 | High |
| CVE-2022-37616 | xmldom | Upgraded to 0.7.9 | Critical |
| CVE-2022-23491 | certifi | Upgraded to 2022.12.7 | High |
| CVE-2021-29060 | color-string | Upgraded to 1.5.5 | Medium |
| CVE-2022-38900 | decode-uri-component | Upgraded to 0.2.1 | High |
| CVE-2020-28469 | glob-parent | Upgraded to 5.1.2 | High |
| CVE-2022-46175 | json5 | Upgraded to 1.0.2 | High |
| CVE-2022-46175 | json5 | Upgraded to 2.2.3 | High |
| CVE-2022-37599 | loader-utils | Upgraded to 2.0.4 | High |
| CVE-2022-37601 | loader-utils | Upgraded to 2.0.4 | Critical |
| CVE-2022-37603 | loader-utils | Upgraded to 2.0.4 | High |
| CVE-2022-3517 | minimatch | Upgraded to 3.0.5 | High |
| CVE-2022-31129 | moment | Upgraded to 2.29.4 | High |
| CVE-2021-23343 | path-parse | Upgraded to 1.0.7 | High |
| CVE-2021-23368 | postcss | Upgraded to 7.0.36 | Medium |
| CVE-2021-23382 | postcss | Upgraded to 7.0.36 | High |
| CVE-2022-43680 | python3 | Upgraded to 3.7.16 | High |
| CVE-2022-24999 | qs | Upgraded to 6.5.3 | High |
| CVE-2020-7753 | ssri | Uppgraded to 6.0.2 | High |
| CVE-2022-25858 | terser | Upgraded to 4.8.1 | High |
| CVE-2021-3803 | nth-check | Upgraded to 2.0.1 | High |
| CVE-2020-7753 | trim | Upgraded to 0.0.3 | High |
| CVE-2021-33587 | css-what | Upgraded to 5.0.1 | High |
| CVE-2020-8116 | dot-prop | Upgraded to 4.2.1 | High |
| CVE-2020-13822 | elliptic | Upgraded to 6.5.4 | High |
| CVE-2022-33987 | got | Upgraded to 12.5.3 | Medium |
| CVE-2022-4200 | jackson-databind | Upgraded to 2.13.5 | Medium |
| CVE-2022-42004 | jackson-databind | Upgraded to 2.13.5 | High |
| CVE-2023-1370 | json-smart | Upgraded to 2.4.9 | High |
| CVE-2019-20149 | kind-of | Upgraded to 6.0.3 | High |
| CVE-2022-37601 | loader-utils | Upgraded to 1.4.2 | Critical |
| CVE-2022-37601 | loader-utils | Upgraded to 2.0.4 | Critical |
| CVE-2020-8203 | lodash | Upgraded to 4.17.21 | High |
| CVE-2019-10744 | lodash-es | Upgraded to 4.17.21 | Critical |
| CVE-2022-40023 | mako | Upgraded to 1.2.4 | High |
| CVE-2019-10746 | mixin-deep | Upgraded to 1.3.2 | Critical |
| CVE-2021-23382 | postcss | Upgraded to 7.0.37 | High |
| CVE-2021-33502 | normalize-url | Upgraded to 6.1.0 | High |
| CVE-2021-27292 | ua-parser-js | Upgraded to 0.7.35 | High |
| CVE-2021-33503 | urllib3 | Upgraded to 1.26.6 | High |
| CVE-2020-7662 | websocket-extensions | Upgraded to 0.1.4 | High |
| CVE-2020-7774 | y18n | Upgraded to 4.0.3 | Critical |
| CVE-2022-23806 | go, crypto/elliptic | Upgraded go to 1.2 | Critical |
| CVE-2022-23772 | go, math/big | Upgraded go to 1.2 | High |
| CVE-2021-43565 | go, x/crypto | Upgraded go to 1.2 | High |
| CVE-2022-30580 | go, os/exec | Upgraded go to 1.2 | High |
| CVE-2022-30633 | go, encoding/xml | Upgraded go to 1.2 | High |
| CVE-2022-28131 | go, encoding/xml | Upgraded go to 1.2 | High |
| CVE-2022-30632 | go, path/filepath | Upgraded go to 1.2 | High |
| CVE-2022-41716 | go | Upgraded go to 1.2 | High |
| CVE-2022-28327 | go, crypto/elliptic | Upgraded go to 1.2 | High |
| CVE-2022-24921 | go | Upgraded go to 1.2 | High |
| CVE-2022-30630 | go, io/fs | Upgraded go to 1.2 | High |
| CVE-2022-27191 | go, crypto/ssh | Upgraded go to 1.2 | High |
| CVE-2022-23773 | go, cmd/go | Upgraded go to 1.2 | High |
| CVE-2022-30634 | go, crypto/rand | Upgraded go to 1.2 | High |
| CVE-2022-41715 | go | Upgraded go to 1.2 | High |
| CVE-2022-24675 | go, encoding/pem | Upgraded go to 1.2 | High |
| CVE-2022-41720 | go | Upgraded go to 1.2 | High |
| CVE-2022-27664 | go, net/http | Upgraded go to 1.2 | High |
| CVE-2022-2880 | go, net/http | Upgraded go to 1.2 | High |
| CVE-2022-29804 | go, path/filepath | Upgraded go to 1.2 | High |
| CVE-2022-32189 | go, math/big | Upgraded go to 1.2 | High |
| CVE-2022-30635 | go, encoding/gob | Upgraded go to 1.2 | High |
| CVE-2022-30631 | go, compress/gzip | Upgraded go to 1.2 | High |
| CVE-2022-2879 | go | Upgraded go to 1.2 | High |
| CVE-2022-1705 | go, net/http | Upgraded go to 1.2 | Medium |
| CVE-2022-1962 | go, go/parse | Upgraded go to 1.2 | Medium |
| CVE-2022-29526 | go, sys | Upgraded go to 1.2 | Medium |
| CVE-2022-32148 | go, net/http | Upgraded go to 1.2 | Medium |
| CVE-2022-30629 | go, crypto/tls | Upgraded go to 1.2 | Low |
| CVE-2017-16042 | Growl | Upgraded to 1.10.5 | Critical |
| CVE-2021-20095 | Babel | Upgraded to 2.9.1 | Medium |
نسخه های تحت تاثیر و اصلاح شده :
| محصول | نسخه | مولفه | نسخه تحت تاثیر |
نسخه اصلاح شده |
|---|---|---|---|---|
| Splunk Enterprise | 8.1 | – | 8.1.13 and Lower | 8.1.14 |
| Splunk Enterprise | 8.2 | – | 8.2.0 to 8.2.10 | 8.2.11 |
| Splunk Enterprise | 9.0 | – | 9.0.0 to 9.0.4 | 9.0.5 |
آسیب پذیری برای برنامه های شخص ثالث در Splunk Cloud برای ژوئن :
اسپلانک آسیب پذیری های زیر رو در نسخه های 9.0.2303.100 و بالاتر اصلاح کرده :
| CVE | Package | Remediation | Severity |
|---|---|---|---|
| CVE-2022-40303 | libxml2 | Patched | High |
| CVE-2022-40304 | libxml2 | Patched | High |
| CVE-2022-23491 | certifi | Upgraded to 2022.12.7 | High |
| CVE-2022-43680 | python3 | Upgraded to 3.7.16 | High |
| CVE-2023-0286 | OpenSSL 1.0.2 | Upgraded to 1.0.2zg | High |
| CVE-2023-0215 | OpenSSL 1.0.2 | Upgraded to 1.0.2zg | High |
| CVE-2022-4304 | OpenSSL 1.0.2 | Upgraded to 1.0.2zg | Medium |
| CVE-2022-33987 | got | Upgraded to 12.5.3 | Medium |
نسخه های تحت تاثیر و اصلاح شده:
| محصول | نسخه | مولفه | نسخه تحت تاثیر |
نسخه اصلاح شده |
|---|---|---|---|---|
| Splunk Cloud | – | 9.0.2303 and lower | 9.0.2303.100 |
آسیب پذیری برای برنامه های شخص ثالث در Splunk Universal Forwarders برای ژوئن :
اسپلانک آسیب پذیری های زیر رو در نسخه های 8.1.14, 8.2.11, 9.0.5 و بالاتر اصلاح کرده :
| CVE | Package | Remediation | Severity |
|---|---|---|---|
| CVE-2022-40303 | libxml2 | Patched | High |
| CVE-2022-40304 | libxml2 | Patched | High |
| CVE-2023-0286 | OpenSSL 1.0.2 | Upgraded to 1.0.2zg | High |
| CVE-2023-0215 | OpenSSL 1.0.2 | Upgraded to 1.0.2zg | High |
| CVE-2022-4304 | OpenSSL 1.0.2 | Upgraded to 1.0.2zg | Medium |
| CVE-2023-27538 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2023-27537 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2023-27536 | curl | Upgraded to 8.0.1 | Critical |
| CVE-2023-27535 | curl | Upgraded to 8.0.1 | High |
| CVE-2023-27534 | curl | Upgraded to 8.0.1 | High |
| CVE-2023-27533 | curl | Upgraded to 8.0.1 | High |
| CVE-2023-23916 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2023-23915 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2023-23914 | curl | Upgraded to 8.0.1 | Critical |
| CVE-2022-43552 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-43551 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-42916 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-42915 | curl | Upgraded to 8.0.1 | Critical |
| CVE-2022-35260 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-32221 | curl | Upgraded to 8.0.1 | Critical |
| CVE-2022-35252 | curl | Upgraded to 8.0.1 | Low |
| CVE-2022-32208 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-32207 | curl | Upgraded to 8.0.1 | Critical |
| CVE-2022-32206 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-32205 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-30115 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-27782 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-27781 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-27780 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-27779 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-27778 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-27776 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-27775 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-27774 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2022-22576 | curl | Upgraded to 8.0.1 | High |
| CVE-2021-22947 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2021-22946 | curl | Upgraded to 8.0.1 | High |
| CVE-2021-22945 | curl | Upgraded to 8.0.1 | Critical |
| CVE-2021-22926 | curl | Upgraded to 8.0.1 | High |
| CVE-2021-22925 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2021-22924 | curl | Upgraded to 8.0.1 | Low |
| CVE-2021-22923 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2021-22922 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2021-22901 | curl | Upgraded to 8.0.1 | High |
| CVE-2021-22898 | curl | Upgraded to 8.0.1 | Low |
| CVE-2021-22897 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2021-22890 | curl | Upgraded to 8.0.1 | Low |
| CVE-2021-22876 | curl | Upgraded to 8.0.1 | Medium |
| CVE-2020-8286 | curl | Upgraded to 8.0.1 | High |
| CVE-2020-8285 | curl | Upgraded to 8.0.1 | High |
| CVE-2020-8284 | curl | Upgraded to 8.0.1 | Low |
| CVE-2020-8231 | curl | Upgraded to 8.0.1 | High |
| CVE-2020-8177 | curl | Upgraded to 8.0.1 | High |
| CVE-2020-8169 | curl | Upgraded to 8.0.1 | High |
| CVE-2022-36227 | libarchive | Upgraded to 3.6.2 | Critical |
| CVE-2021-31566 | libarchive | Upgraded to 3.6.2 | High |
| CVE-2021-36976 | libarchive | Upgraded to 3.6.2 | Medium |
| CVE-2021-3520 | lz4 | Upgraded to 1.9.4 | Critical |
| CVE-2022-35737 | SQLite | Upgraded to 3.41.2 | High |
| CVE-2018-25032 | zlib | Applied patch | High |
| CVE-2022-37434 | zlib | Applied patch | Critical |
نسخه های تحت تاثیر و اصلاح شده:
| محصول | نسخه | مولفه | نسخه های تحت تاثیر |
نسخه اصلاح شده |
|---|---|---|---|---|
| Universal Forwarders | 8.1 | – | 8.1.13 and Lower | 8.1.14 |
| Universal Forwarders | 8.2 | – | 8.2.0 to 8.2.10 | 8.2.11 |
| Universal Forwarders | 9.0 | – | 9.0.0 to 9.0.4 | 9.0.5 |