Ansible Tower における入力確認に関する脆弱性
| Title |
Ansible Tower における入力確認に関する脆弱性
|
| Summary |
Ansible Tower には、入力確認に関する脆弱性が存在します。
|
| Possible impacts |
情報を取得される、情報を改ざんされる、およびサービス運用妨害 (DoS) 状態にされる可能性があります。 |
| Solution |
ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。 |
| Publication Date |
Oct. 24, 2017, midnight |
| Registration Date |
Oct. 29, 2018, 12:10 p.m. |
| Last Update |
Oct. 29, 2018, 12:10 p.m. |
|
CVSS3.0 : 重要
|
| Score |
7.2
|
| Vector |
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
|
CVSS2.0 : 危険
|
| Score |
9
|
| Vector |
AV:N/AC:L/Au:S/C:C/I:C/A:C |
Affected System
| レッドハット |
|
Ansible Tower 3.1.5 未満
|
|
Ansible Tower 3.2.0 未満
|
|
Red Hat CloudForms
|
CVE (情報セキュリティ 共通脆弱性識別子)
CWE (共通脆弱性タイプ一覧)
ベンダー情報
Change Log
| No |
Changed Details |
Date of change |
| 1 |
[2018年10月29日]
掲載 |
Oct. 29, 2018, 12:10 p.m. |
NVD Vulnerability Information
CVE-2017-12148
| Summary |
A flaw was found in Ansible Tower's interface before 3.1.5 and 3.2.0 with SCM repositories. If a Tower project (SCM repository) definition does not have the 'delete before update' flag set, an attacker with commit access to the upstream playbook source repository could create a Trojan playbook that, when executed by Tower, modifies the checked out SCM repository to add git hooks. These git hooks could, in turn, cause arbitrary command and code execution as the user Tower runs as.
|
| Publication Date |
July 28, 2018, 1:29 a.m. |
| Registration Date |
Jan. 26, 2021, 1:13 p.m. |
| Last Update |
Nov. 21, 2024, 12:08 p.m. |
Affected software configurations
| Configuration1 |
or higher |
or less |
more than |
less than |
| cpe:2.3:a:redhat:cloudforms:4.5:*:*:*:*:*:*:* |
|
|
|
|
| cpe:2.3:a:redhat:ansible_tower:*:*:*:*:*:*:*:* |
|
|
|
3.1.5 |
| cpe:2.3:a:redhat:ansible_tower:*:*:*:*:scm_repositories:*:*:* |
|
|
|
3.2.0 |
Related information, measures and tools
Common Vulnerabilities List