Back to bug 1818445
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Borja Tarraso | 2020-03-28 07:22:58 UTC | CC | security-response-team | |
| Borja Tarraso | 2020-03-29 06:36:50 UTC | Group | security, qe_staff | |
| Summary | EMBARGOED Tower: memcached deployment is insecure on OpenShift | Tower: memcached deployment is insecure on OpenShift | ||
| Borja Tarraso | 2020-03-29 06:37:32 UTC | Depends On | 1818543, 1818545, 1818544 | |
| RaTasha Tillery-Smith | 2020-03-30 12:52:02 UTC | Summary | Tower: memcached deployment is insecure on OpenShift | CVE-2020-10697 Tower: memcached deployment is insecure on OpenShift |
| Alias | CVE-2020-10697 | |||
| Doc Text | A flaw was found in Ansible Tower when running Openshift. Tower runs a memcached which is accessed via TCP. An attacker could take advantage writing a playbook polluting this cache causing a DoS (Denial of Service) attack. This would not be able to stop completely the service but in the worst case reduce the Tower performance, as memcached is what actually is designed for. Theoretically more complex attacks could be performed by manipulating and crafting the cache as Tower relies on memcached as a place to pull out setting values. Not any confidentiality and sensitive data stored in memcached can be pulled out as this would be encrypted. | A flaw was found in Ansible Tower when running Openshift. Tower runs a memcached, which is accessed via TCP. An attacker can take advantage of writing a playbook polluting this cache, causing a denial of service attack. This attack would not completely stop the service, but in the worst-case scenario, it can reduce the Tower performance, for which memcached is designed. Theoretically, more sophisticated attacks can be performed by manipulating and crafting the cache, as Tower relies on memcached as a place to pull out setting values. Confidential and sensitive data stored in memcached should not be pulled, as this information is encrypted. | ||
| Doc Type | --- | If docs needed, set a value | ||
| Jeff Needle | 2020-03-31 14:30:44 UTC | CC | jneedle | |
| Red Hat Bugzilla | 2021-01-26 11:47:21 UTC | CC | gmainwar | |
| Red Hat Bugzilla | 2021-04-20 07:45:16 UTC | CC | rpetrell | |
| Red Hat Bugzilla | 2021-11-02 15:41:54 UTC | CC | notting | |
| Red Hat Bugzilla | 2021-12-15 11:50:47 UTC | CC | cmeyers | |
| Red Hat Bugzilla | 2023-07-07 08:31:59 UTC | CC | security-response-team | |
| Assignee | security-response-team | nobody |
Back to bug 1818445