Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

fstec логотип

BDU:2024-11473

Опубликовано: 04 мая 2024
Источник: fstec
CVSS3: 4.4
CVSS2: 3.2
EPSS Низкий

Описание

Уязвимость файловой системы tracefs ядра операционной системы Linux связана с недостатками разграничения доступа. Эксплуатация уязвимости может позволить нарушителю получить доступ на чтение, изменение или удаление данных

Вендор

ООО «Ред Софт»
Сообщество свободного программного обеспечения
АО "НППКТ"
ООО «РусБИТех-Астра»

Наименование ПО

РЕД ОС
Linux
ОСОН ОСнова Оnyx
Astra Linux Special Edition

Версия ПО

7.3 (РЕД ОС)
от 6.7.4 до 6.8.9 включительно (Linux)
до 2.11 (ОСОН ОСнова Оnyx)
1.8 (Astra Linux Special Edition)
от 6.6.18 до 6.6.30 включительно (Linux)

Тип ПО

Операционная система

Операционные системы и аппаратные платформы

ООО «Ред Софт» РЕД ОС 7.3
АО "НППКТ" ОСОН ОСнова Оnyx до 2.11
ООО «РусБИТех-Астра» Astra Linux Special Edition 1.8
Сообщество свободного программного обеспечения Linux от 6.8 до 6.8.10
Сообщество свободного программного обеспечения Linux от 6.6.18 до 6.6.31
Сообщество свободного программного обеспечения Linux от 6.9 до 6.9 rc7

Уровень опасности уязвимости

Низкий уровень опасности (базовая оценка CVSS 2.0 составляет 3,2)
Средний уровень опасности (базовая оценка CVSS 3.0 составляет 4,4)

Возможные меры по устранению уязвимости

Использование рекомендаций:
Для Linux:
https://git.kernel.org/stable/c/414fb08628143203d29ccd0264b5a83fb9523c03
https://git.kernel.org/stable/c/5f91fc82794d4a6e41cdcd02d00baa377d94ca78
https://git.kernel.org/stable/c/baa23a8d4360d981a49913841a726edede5cdd54
https://lore.kernel.org/linux-cve-announce/2024060344-CVE-2024-36963-b8cc@gregkh/
Для РедОС:
http://repo.red-soft.ru/redos/7.3c/x86_64/updates/
Обновление программного обеспечения linux до версии 6.6.36-0.osnova233
Для ОС Astra Linux:
- обновить пакет linux-6.6 до 6.12.11-1.astra1+ci18 или более высокой версии, используя рекомендации производителя: https://wiki.astralinux.ru/astra-linux-se18-bulletin-2025-0411SE18

Статус уязвимости

Подтверждена производителем

Наличие эксплойта

Данные уточняются

Информация об устранении

Уязвимость устранена

Идентификаторы других систем описаний уязвимостей

EPSS

Процентиль: 12%
0.0004
Низкий

4.4 Medium

CVSS3

3.2 Low

CVSS2

Связанные уязвимости

CVSS3: 7.8
ubuntu
около 1 года назад

In the Linux kernel, the following vulnerability has been resolved: tracefs: Reset permissions on remount if permissions are options There's an inconsistency with the way permissions are handled in tracefs. Because the permissions are generated when accessed, they default to the root inode's permission if they were never set by the user. If the user sets the permissions, then a flag is set and the permissions are saved via the inode (for tracefs files) or an internal attribute field (for eventfs). But if a remount happens that specify the permissions, all the files that were not changed by the user gets updated, but the ones that were are not. If the user were to remount the file system with a given permission, then all files and directories within that file system should be updated. This can cause security issues if a file's permission was updated but the admin forgot about it. They could incorrectly think that remounting with permissions set would update all files, but miss some. ...

CVSS3: 4.4
redhat
около 1 года назад

In the Linux kernel, the following vulnerability has been resolved: tracefs: Reset permissions on remount if permissions are options There's an inconsistency with the way permissions are handled in tracefs. Because the permissions are generated when accessed, they default to the root inode's permission if they were never set by the user. If the user sets the permissions, then a flag is set and the permissions are saved via the inode (for tracefs files) or an internal attribute field (for eventfs). But if a remount happens that specify the permissions, all the files that were not changed by the user gets updated, but the ones that were are not. If the user were to remount the file system with a given permission, then all files and directories within that file system should be updated. This can cause security issues if a file's permission was updated but the admin forgot about it. They could incorrectly think that remounting with permissions set would update all files, but miss some. ...

CVSS3: 7.8
nvd
около 1 года назад

In the Linux kernel, the following vulnerability has been resolved: tracefs: Reset permissions on remount if permissions are options There's an inconsistency with the way permissions are handled in tracefs. Because the permissions are generated when accessed, they default to the root inode's permission if they were never set by the user. If the user sets the permissions, then a flag is set and the permissions are saved via the inode (for tracefs files) or an internal attribute field (for eventfs). But if a remount happens that specify the permissions, all the files that were not changed by the user gets updated, but the ones that were are not. If the user were to remount the file system with a given permission, then all files and directories within that file system should be updated. This can cause security issues if a file's permission was updated but the admin forgot about it. They could incorrectly think that remounting with permissions set would update all files, but miss some.

CVSS3: 7.8
debian
около 1 года назад

In the Linux kernel, the following vulnerability has been resolved: t ...

CVSS3: 7.8
github
около 1 года назад

In the Linux kernel, the following vulnerability has been resolved: tracefs: Reset permissions on remount if permissions are options There's an inconsistency with the way permissions are handled in tracefs. Because the permissions are generated when accessed, they default to the root inode's permission if they were never set by the user. If the user sets the permissions, then a flag is set and the permissions are saved via the inode (for tracefs files) or an internal attribute field (for eventfs). But if a remount happens that specify the permissions, all the files that were not changed by the user gets updated, but the ones that were are not. If the user were to remount the file system with a given permission, then all files and directories within that file system should be updated. This can cause security issues if a file's permission was updated but the admin forgot about it. They could incorrectly think that remounting with permissions set would update all files, but miss so...

EPSS

Процентиль: 12%
0.0004
Низкий

4.4 Medium

CVSS3

3.2 Low

CVSS2