| Title | AppArmor におけるアクセス制御に関する脆弱性 |
|---|---|
| Summary | AppArmor には、アクセス制御に関する脆弱性が存在します。 |
| Possible impacts | 情報を改ざんされる可能性があります。 |
| Solution | ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。 |
| Publication Date | March 21, 2017, midnight |
| Registration Date | April 27, 2017, 4:35 p.m. |
| Last Update | April 27, 2017, 4:35 p.m. |
| CVSS3.0 : 警告 | |
| Score | 5.9 |
|---|---|
| Vector | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N |
| CVSS2.0 : 警告 | |
| Score | 4.3 |
|---|---|
| Vector | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| Canonical |
| Ubuntu Core 15.04 |
| Ubuntu Touch 15.04 |
| AppArmor project |
| AppArmor 2.12 未満 |
| No | Changed Details | Date of change |
|---|---|---|
| 0 | [2017年04月27日] 掲載 |
Feb. 17, 2018, 10:37 a.m. |
| Summary | An issue was discovered in AppArmor before 2.12. Incorrect handling of unknown AppArmor profiles in AppArmor init scripts, upstart jobs, and/or systemd unit files allows an attacker to possibly have increased attack surfaces of processes that were intended to be confined by AppArmor. This is due to the common logic to handle 'restart' operations removing AppArmor profiles that aren't found in the typical filesystem locations, such as /etc/apparmor.d/. Userspace projects that manage their own AppArmor profiles in atypical directories, such as what's done by LXD and Docker, are affected by this flaw in the AppArmor init script logic. |
|---|---|
| Publication Date | March 24, 2017, 4:59 p.m. |
| Registration Date | Jan. 26, 2021, 1:27 p.m. |
| Last Update | Nov. 21, 2024, 12:29 p.m. |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:a:apparmor:apparmor:*:*:*:*:*:*:*:* | 2.11 | ||||
| Configuration2 | or higher | or less | more than | less than | |
| cpe:2.3:o:canonical:ubuntu_touch:15.04:*:*:*:*:*:*:* | |||||
| cpe:2.3:o:canonical:ubuntu_core:15.04:*:*:*:*:*:*:* | |||||