Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
ver any existing account (guest or normal one). The issue has been patched in Sylius 1.6.9, 1.7.9 and 1.8.3. As a workaround, you may resolve this issue on your own by creating a custom event listener, which will listen to the sylius.customer.pre_update event. You can determine that email has been changed if customer email and user username are different. They are synchronized later on. Pay attention, to email changing behavior for administrators. You may need to skip this logic for them. In order to achieve this, you should either check master request path info, if it does not contain /admin prefix or adjust event triggered during customer update in the shop. You can find more information o
not contain /admin prefix or adjust event triggered during customer update in the shop. You can find more information on how to customize the event here. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/Sylius/Sylius/security/advisories/GHSA-6gw4-x63h-5499 - https://github.com/Sylius/Sylius/commit/60636d711a4011e8694d10d201b53632c7e8ecaf
CVE ID: CVE-2020-15246 State: PUBLISHED Published: 2020-11-23T19:25:14 Last Updated: 2024-08-04T13:08:23.211Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) Vendors: octobercms Products: october Problem Types: CWE-863 Description: October is a free, open-source, self-hosted CMS platform based on the Laravel PHP Framework. In October CMS from version 1.0.421 and before version 1.0.469, an attacker can read local files on an October CMS server via a specially crafted request. Issue has been patched in Build 469 (v1.0.469) and v1.1.0. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/octobercms/october/security/advisories/GHSA-xwjr-6fj7-
Notes: - CVE Program Container: References: - https://github.com/octobercms/october/security/advisories/GHSA-xwjr-6fj7-fc6h - https://github.com/octobercms/library/commit/80aab47f044a2660aa352450f55137598f362aa4
CVE ID: CVE-2020-15247 State: PUBLISHED Published: 2020-11-23T19:35:14 Last Updated: 2024-08-04T13:08:23.232Z Severity: MEDIUM (CVSS 5.2 CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L) Vendors: octobercms Products: october Problem Types: CWE-862 Description: October is a free, open-source, self-hosted CMS platform based on the Laravel PHP Framework. In October CMS from version 1.0.319 and before version 1.0.469, an authenticated backend user with the cms.manage_pages, cms.manage_layouts, or cms.manage_partials permissions who would normally not be permitted to provide PHP code to be executed by the CMS due to cms.enableSafeMode being enabled is able to write specific Twig code to escape the Tw
e to be executed by the CMS due to cms.enableSafeMode being enabled is able to write specific Twig code to escape the Twig sandbox and execute arbitrary PHP. This is not a problem for anyone that trusts their users with those permissions to normally write & manage PHP within the CMS by not having cms.enableSafeMode enabled, but would be a problem for anyone relying on cms.enableSafeMode to ensure that users with those permissions in production do not have access to write & execute arbitrary PHP. Issue has been patched in Build 469 (v1.0.469) and v1.1.0. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/octobercms/october/security/advisories/GHSA-94vp-rmqv-58
otes: - CVE Program Container: References: - https://github.com/octobercms/october/security/advisories/GHSA-94vp-rmqv-5875 - https://github.com/octobercms/october/commit/4c650bb775ab849e48202a4923bac93bd74f9982
CVE ID: CVE-2020-15248 State: PUBLISHED Published: 2020-11-23T19:40:15 Last Updated: 2024-08-04T13:08:23.177Z Severity: MEDIUM (CVSS 4 CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:L) Vendors: octobercms Products: october Problem Types: CWE-863 Description: October is a free, open-source, self-hosted CMS platform based on the Laravel PHP Framework. In October CMS from version 1.0.319 and before version 1.0.470, backend users with the default "Publisher" system role have access to create & manage users where they can choose which role the new user has. This means that a user with "Publisher" access has the ability to escalate their access to "Developer" access. Issue has been patched in Build 47
th "Publisher" access has the ability to escalate their access to "Developer" access. Issue has been patched in Build 470 (v1.0.470) & v1.1.1. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/octobercms/october/security/advisories/GHSA-rfjc-xrmf-5vvw - https://github.com/octobercms/october/commit/78a37298a4ed4602b383522344a31e311402d829
CVE ID: CVE-2020-15249 State: PUBLISHED Published: 2020-11-23T19:50:14 Last Updated: 2024-08-04T13:08:23.190Z Severity: LOW (CVSS 2.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N) Vendors: octobercms Products: october Problem Types: CWE-79 Description: October is a free, open-source, self-hosted CMS platform based on the Laravel PHP Framework. In October CMS from version 1.0.319 and before version 1.0.469, backend users with access to upload files were permitted to upload SVG files without any sanitization applied to the uploaded files. Since SVG files support being parsed as HTML by browsers, this means that they could theoretically upload Javascript that would be executed on a path under t
as HTML by browsers, this means that they could theoretically upload Javascript that would be executed on a path under the website's domain (i.e. /storage/app/media/evil.svg), but they would have to convince their target to visit that location directly in the target's browser as the backend does not display SVGs inline anywhere, SVGs are only displayed as image resources in the backend and are thus unable to be executed. Issue has been patched in Build 469 (v1.0.469) & v1.1.0. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/octobercms/library/commit/80aab47f044a2660aa352450f55137598f362aa4 - https://github.com/octobercms/october/security/advisories/GHSA-fx
rary/commit/80aab47f044a2660aa352450f55137598f362aa4 - https://github.com/octobercms/october/security/advisories/GHSA-fx3v-553x-3c4q
CVE ID: CVE-2020-15250 State: PUBLISHED Published: 2020-10-12T17:55:13 Last Updated: 2024-08-04T13:08:23.218Z Severity: MEDIUM (CVSS 4.4 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N) Vendors: junit-team Products: junit4 Problem Types: CWE-200 Description: In JUnit4 from version 4.7 and before 4.13.1, the test rule TemporaryFolder contains a local information disclosure vulnerability. On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system. This vulnerability does not allow other users to overwrite the contents
lt, readable by other users on that same system. This vulnerability does not allow other users to overwrite the contents of these directories or files. This is purely an information disclosure vulnerability. This vulnerability impacts you if the JUnit tests write sensitive information, like API keys or passwords, into the temporary folder, and the JUnit tests execute in an environment where the OS has other untrusted users. Because certain JDK file system APIs were only added in JDK 1.7, this this fix is dependent upon the version of the JDK you are using. For Java 1.7 and higher users: this vulnerability is fixed in 4.13.1. For Java 1.6 and lower users: no patch is available, you must use t
higher users: this vulnerability is fixed in 4.13.1. For Java 1.6 and lower users: no patch is available, you must use the workaround below. If you are unable to patch, or are stuck running on Java 1.6, specifying the `java.io.tmpdir` system environment variable to a directory that is exclusively owned by the executing user will fix this vulnerability. For more information, including an example of vulnerable code, see the referenced GitHub Security Advisory. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp - https://github.com/junit-team/junit4/commit/610155b8c22138329f0723eec22521627dbc52ae - https:
ries/GHSA-269g-pwp5-87pp - https://github.com/junit-team/junit4/commit/610155b8c22138329f0723eec22521627dbc52ae - https://github.com/junit-team/junit4/blob/7852b90cfe1cea1e0cdaa19d490c83f0d8684b50/doc/ReleaseNotes4.13.1.md - https://junit.org/junit4/javadoc/4.13/org/junit/rules/TemporaryFolder.html - https://lists.apache.org/thread.html/r5f8841507576f595bb783ccec6a7cb285ea90d4e6f5043eae0e61a41%40%3Cdev.creadur.apache.org%3E - https://lists.apache.org/thread.html/rbaec90e699bc7c7bd9a053f76707a36fda48b6d558f31dc79147dbf9%40%3Cdev.creadur.apache.org%3E - https://lists.apache.org/thread.html/r717877028482c55acf604d7a0106af4ca05da4208c708fb157b53672%40%3Ccommits.creadur.apache.org%3E - https://li
rg/thread.html/r717877028482c55acf604d7a0106af4ca05da4208c708fb157b53672%40%3Ccommits.creadur.apache.org%3E - https://lists.apache.org/thread.html/rb2771949c676ca984e58a5cd5ca79c2634dee1945e0406e48e0f8457%40%3Cdev.creadur.apache.org%3E - https://lists.apache.org/thread.html/rde385b8b53ed046600ef68dd6b4528dea7566aaddb02c3e702cc28bc%40%3Ccommits.creadur.apache.org%3E - https://lists.apache.org/thread.html/rc49cf1547ef6cac1be4b3c92339b2cae0acacf5acaba13cfa429a872%40%3Cdev.creadur.apache.org%3E - https://lists.apache.org/thread.html/r500517c23200fb2fdb0b82770a62dd6c88b3521cfb01cfd0c76e3f8b%40%3Cdev.creadur.apache.org%3E - https://lists.apache.org/thread.html/r95f8ef60c4b3a5284b647bb3132cda08e6fa
cfd0c76e3f8b%40%3Cdev.creadur.apache.org%3E - https://lists.apache.org/thread.html/r95f8ef60c4b3a5284b647bb3132cda08e6fadad888a66b84f49da0b0%40%3Ccommits.creadur.apache.org%3E - https://github.com/junit-team/junit4/issues/1676 - https://lists.debian.org/debian-lts-announce/2020/11/msg00003.html - https://lists.apache.org/thread.html/ra1bdb9efae84794e8ffa2f8474be8290ba57830eefe9714b95da714b%40%3Cdev.pdfbox.apache.org%3E - https://lists.apache.org/thread.html/rb33212dab7beccaf1ffef9b88610047c644f644c7a0ebdc44d77e381%40%3Ccommits.turbine.apache.org%3E - https://lists.apache.org/thread.html/raebf13f53cd5d23d990712e3d11c80da9a7bae94a6284050f148ed99%40%3Ccommits.pulsar.apache.org%3E - https://list
g/thread.html/raebf13f53cd5d23d990712e3d11c80da9a7bae94a6284050f148ed99%40%3Ccommits.pulsar.apache.org%3E - https://lists.apache.org/thread.html/r01110833b63616ddbef59ae4e10c0fbd0060f0a51206defd4cb4d917%40%3Ccommits.pulsar.apache.org%3E - https://lists.apache.org/thread.html/rde8e70b95c992378e8570e4df400c6008a9839eabdfb8f800a3e5af6%40%3Ccommits.pulsar.apache.org%3E - https://lists.apache.org/thread.html/rdef7d1380c86e7c0edf8a0f89a2a8db86fce5e363457d56b722691b4%40%3Ccommits.pulsar.apache.org%3E - https://lists.apache.org/thread.html/rdbdd30510a7c4d0908fd22075c02b75bbc2e0d977ec22249ef3133cb%40%3Ccommits.pulsar.apache.org%3E - https://lists.apache.org/thread.html/rea812d8612fdc46842a2a57248cad4
ec22249ef3133cb%40%3Ccommits.pulsar.apache.org%3E - https://lists.apache.org/thread.html/rea812d8612fdc46842a2a57248cad4b01ddfdb1e9b037c49e68fdbfb%40%3Ccommits.pulsar.apache.org%3E - https://lists.apache.org/thread.html/rf797d119cc3f51a8d7c3c5cbe50cb4524c8487282b986edde83a9467%40%3Ccommits.pulsar.apache.org%3E - https://lists.apache.org/thread.html/reb700e60b9642eafa4b7922bfee80796394135aa09c7a239ef9f7486%40%3Ccommits.pulsar.apache.org%3E - https://lists.apache.org/thread.html/rf2ec93f4ca9a97d1958eb4a31b1830f723419ce9bf2018a6e5741d5b%40%3Ccommits.pulsar.apache.org%3E - https://lists.apache.org/thread.html/r30f502d2f79e8d635361adb8108dcbb73095163fcbd776ee7984a094%40%3Ccommits.creadur.apache.o
s://lists.apache.org/thread.html/r30f502d2f79e8d635361adb8108dcbb73095163fcbd776ee7984a094%40%3Ccommits.creadur.apache.org%3E - https://lists.apache.org/thread.html/r925eaae7dd8f77dd61eefc49c1fcf54bd9ecfe605486870d7b1e9390%40%3Cpluto-dev.portals.apache.org%3E - https://lists.apache.org/thread.html/r29d703d1986d9b871466ff24082a1828ac8ad27bb0965a93a383872e%40%3Cpluto-scm.portals.apache.org%3E - https://lists.apache.org/thread.html/r09cfbb5aedd76023691bbce9ca4ce2e16bb07dd37554a17efc19935d%40%3Cpluto-dev.portals.apache.org%3E - https://lists.apache.org/thread.html/r2b78f23bc2711a76a7fc73ad67b7fcd6817c5cfccefd6f30a4f54943%40%3Cdev.knox.apache.org%3E - https://lists.apache.org/thread.html/rf6e5d89
1a76a7fc73ad67b7fcd6817c5cfccefd6f30a4f54943%40%3Cdev.knox.apache.org%3E - https://lists.apache.org/thread.html/rf6e5d894d4b03bef537c9d6641272e0197c047c0d1982b4e176d0353%40%3Cdev.knox.apache.org%3E - https://lists.apache.org/thread.html/r687f489b10b0d14e46f626aa88476545e1a2600b24c4ebd3c0d2a10b%40%3Cdev.knox.apache.org%3E - https://lists.apache.org/thread.html/r934208a520b38f5cf0cae199b6b076bfe7d081809528b0eff2459e40%40%3Cdev.knox.apache.org%3E - https://lists.apache.org/thread.html/r8b02dc6f18df11ff39eedb3038f1e31e6f90a779b1959bae65107279%40%3Cdev.knox.apache.org%3E - https://lists.apache.org/thread.html/r9710067c7096b83cb6ae8f53a2f6f94e9c042d1bf1d6929f8f2a2b7a%40%3Ccommits.knox.apache.org%3
://lists.apache.org/thread.html/r9710067c7096b83cb6ae8f53a2f6f94e9c042d1bf1d6929f8f2a2b7a%40%3Ccommits.knox.apache.org%3E - https://lists.apache.org/thread.html/r1209986f79359b518d09513ff05a88e5b3c398540e775edea76a4774%40%3Cdev.knox.apache.org%3E - https://lists.apache.org/thread.html/r742b44fd75215fc75963b8ecc22b2e4372e68d67d3d859d2b5e8743f%40%3Cdev.knox.apache.org%3E - https://lists.apache.org/thread.html/rb2ffe2993f4dccc48d832e1a0f1c419477781b6ea16e725ca2276dbb%40%3Cdev.knox.apache.org%3E - https://www.oracle.com/security-alerts/cpuapr2022.html
CVE ID: CVE-2020-15251 State: PUBLISHED Published: 2020-10-13T17:15:17 Last Updated: 2024-08-04T13:08:23.235Z Severity: HIGH (CVSS 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N) Vendors: MirahezeBots Products: sopel-channelmgnt Problem Types: CWE-863 Description: In the Channelmgnt plug-in for Sopel (a Python IRC bot) before version 1.0.3, malicious users are able to op/voice and take over a channel. This is an ACL bypass vulnerability. This plugin is bundled with MirahezeBot-Plugins with versions from 9.0.0 and less than 9.0.2 affected. Version 9.0.2 includes 1.0.3 of channelmgnt, and thus is safe from this vulnerability. See referenced GHSA-23pc-4339-95vg. Additional Analyst Notes: - CV
hannelmgnt, and thus is safe from this vulnerability. See referenced GHSA-23pc-4339-95vg. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/MirahezeBots/sopel-channelmgnt/security/advisories/GHSA-j257-jfvv-h3x5 - https://github.com/MirahezeBots/sopel-channelmgnt/pull/3 - https://phab.bots.miraheze.wiki/T117 - https://pypi.org/project/sopel-plugins.channelmgnt/ - https://github.com/MirahezeBots/MirahezeBots/security/advisories/GHSA-23pc-4339-95vg - https://phab.bots.miraheze.wiki/phame/live/1/post/1/summary/
CVE ID: CVE-2020-15252 State: PUBLISHED Published: 2020-10-16T16:55:17 Last Updated: 2024-08-04T13:08:23.190Z Severity: HIGH (CVSS 8.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H) Vendors: xwiki Products: xwiki-platform Problem Types: CWE-94 Description: In XWiki before version 12.5 and 11.10.6, any user with SCRIPT right (EDIT right before XWiki 7.4) can gain access to the application server Servlet context which contains tools allowing to instantiate arbitrary Java objects and invoke methods that may lead to arbitrary code execution. This is patched in XWiki 12.5 and XWiki 11.10.6. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/xwiki/xwiki-platform/sec
ki 11.10.6. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-5hv6-mh8q-q9v8 - https://jira.xwiki.org/browse/XWIKI-17141 - https://jira.xwiki.org/browse/XWIKI-17423
CVE ID: CVE-2020-15253 State: PUBLISHED Published: 2020-10-14T18:15:21 Last Updated: 2024-08-04T13:08:22.823Z Severity: HIGH (CVSS 7.3 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N) Vendors: grocy Products: grocy Problem Types: CWE-79 Description: Versions of Grocy <= 2.7.1 are vulnerable to Cross-Site Scripting via the Create Shopping List module, that is rendered upon deleting that Shopping List. The issue was also found in users, batteries, chores, equipment, locations, quantity units, shopping locations, tasks, taskcategories, product groups, recipes and products. Authentication is required to exploit these issues and Grocy should not be publicly exposed. The linked reference details a pr
tication is required to exploit these issues and Grocy should not be publicly exposed. The linked reference details a proof-of-concept. Additional Analyst Notes: - CVE Program Container: References: - https://www.exploit-db.com/exploits/48792 - https://github.com/grocy/grocy/security/advisories/GHSA-7f37-2fjr-v9p7 - https://github.com/grocy/grocy/issues/996 - https://github.com/grocy/grocy/commit/0624b0df594a4353ef25e6b1874565ea52ce7772 - https://github.com/grocy/grocy/commit/0df2590de27c60c18b7db6e056347bd2aff5a887
CVE ID: CVE-2020-15254 State: PUBLISHED Published: 2020-10-16T17:05:24 Last Updated: 2024-08-04T13:08:23.227Z Severity: HIGH (CVSS 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) Vendors: crossbeam-rs Products: crossbeam Problem Types: CWE-119 Description: Crossbeam is a set of tools for concurrent programming. In crossbeam-channel before version 0.4.4, the bounded channel incorrectly assumes that `Vec::from_iter` has allocated capacity that same as the number of iterator elements. `Vec::from_iter` does not actually guarantee that and may allocate extra memory. The destructor of the `bounded` channel reconstructs `Vec` from the raw pointer based on the incorrect assumes described above. Th
ctor of the `bounded` channel reconstructs `Vec` from the raw pointer based on the incorrect assumes described above. This is unsound and causing deallocation with the incorrect capacity when `Vec::from_iter` has allocated different sizes with the number of iterator elements. This has been fixed in crossbeam-channel 0.4.4. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/crossbeam-rs/crossbeam/security/advisories/GHSA-v5m7-53cv-f3hx - https://github.com/crossbeam-rs/crossbeam/issues/539 - https://github.com/crossbeam-rs/crossbeam/pull/533 - https://github.com/RustSec/advisory-db/pull/425
CVE ID: CVE-2020-15255 State: PUBLISHED Published: 2020-10-16T16:20:16 Last Updated: 2024-08-04T13:08:23.253Z Severity: HIGH (CVSS 8.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) Vendors: anuko Products: timetracker Problem Types: CWE-74 Description: In Anuko Time Tracker before verion 1.19.23.5325, due to not properly filtered user input a CSV export of a report could contain cells that are treated as formulas by spreadsheet software (for example, when a cell value starts with an equal sign). This is fixed in version 1.19.23.5325. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/anuko/timetracker/security/advisories/GHSA-prjf-9mgh-8fpv - https://github.c
Container: References: - https://github.com/anuko/timetracker/security/advisories/GHSA-prjf-9mgh-8fpv - https://github.com/anuko/timetracker/commit/d9472904361495f318c9d0294ffd28acaaeae42f - http://packetstormsecurity.com/files/159996/Anuko-Time-Tracker-1.19.23.5325-CSV-Injection.html - https://www.exploit-db.com/exploits/49027
CVE ID: CVE-2020-15256 State: PUBLISHED Published: 2020-10-19T21:25:13 Last Updated: 2024-08-04T13:08:23.212Z Severity: HIGH (CVSS 7.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H) Vendors: mariocasciaro Products: object-path Problem Types: CWE-471, CWE-20 Description: A prototype pollution vulnerability has been found in `object-path` <= 0.11.4 affecting the `set()` method. The vulnerability is limited to the `includeInheritedProps` mode (if version >= 0.11.0 is used), which has to be explicitly enabled by creating a new instance of `object-path` and setting the option `includeInheritedProps: true`, or by using the default `withInheritedProps` instance. The default operating mode is not aff
cludeInheritedProps: true`, or by using the default `withInheritedProps` instance. The default operating mode is not affected by the vulnerability if version >= 0.11.0 is used. Any usage of `set()` in versions < 0.11.0 is vulnerable. The issue is fixed in object-path version 0.11.5 As a workaround, don't use the `includeInheritedProps: true` options or the `withInheritedProps` instance if using a version >= 0.11.0. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/mariocasciaro/object-path/security/advisories/GHSA-cwx2-736x-mf6w - https://github.com/mariocasciaro/object-path/commit/2be3354c6c46215c7635eb1b76d80f1319403c68
CVE ID: CVE-2020-15257 State: PUBLISHED Published: 2020-12-01T02:30:16 Last Updated: 2024-08-04T13:15:19.030Z Severity: MEDIUM (CVSS 5.2 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) Vendors: containerd Products: containerd Problem Types: CWE-669 Description: containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious contain
e UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users to start containers in t
o be vulnerable even after an upgrade. If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the "host" network namespace, for example with docker run --net=host or hostNetwork: true in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue. If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to deny unix addr=@**, to your policy. It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly ad
h a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container. Additional Analyst Notes: - CVE Program Container: References: - https://github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4 - https://github.com/containerd/containerd/commit/4a4bb851f5da563ff6e68a83dc837c7699c469ad - https://github.com/containerd/containerd/releases/tag/v1.4.3 - https://lists.fedoraproject.org/archives/list/
99c469ad - https://github.com/containerd/containerd/releases/tag/v1.4.3 - https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LNKXLOLZWO5FMAPX63ZL7JNKTNNT5NQD/ - https://www.debian.org/security/2021/dsa-4865 - https://security.gentoo.org/glsa/202105-33