Back to bug 1829674
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Dhananjay Arunesh | 2020-04-30 05:12:48 UTC | Summary | openshift/apb-tools: permissive sudoers file | CVE-2020-10728 openshift/apb-tools: permissive sudoers file |
| Alias | CVE-2020-10728 | |||
| Mark Cooper | 2020-04-30 06:05:30 UTC | Depends On | 1829688, 1829690, 1829689 | |
| Marc O'Brien | 2020-04-30 15:44:36 UTC | Status | NEW | ASSIGNED |
| CC | marobrie | |||
| Doc Type | --- | If docs needed, set a value | ||
| Jesus M. Rodriguez | 2020-04-30 21:12:26 UTC | CC | jesusr | |
| Mark Cooper | 2020-05-01 02:04:48 UTC | Doc Text | An incorrect privilege assignment vulnerability was found in openshift/apb-tools. An attacker with access to the container could use this flaw to escalate their privileges. | An incorrect privilege assignment vulnerability was found in automationbroker/apb. An attacker with access to the container could use this flaw to escalate their privileges. |
| Summary | CVE-2020-10728 openshift/apb-tools: permissive sudoers file | CVE-2020-10728 automationbroker/apb: permissive sudoers file | ||
| Mark Cooper | 2020-05-01 02:06:12 UTC | Comment | 0 | updated |
| Eric Christensen | 2020-05-01 17:59:03 UTC | Doc Text | An incorrect privilege assignment vulnerability was found in automationbroker/apb. An attacker with access to the container could use this flaw to escalate their privileges. | A flaw was found in automationbroker/apb container in versions up to and including 2.0.4-1. This container grants all users sudoer permissions allowing an unauthorized user with access to the running container the ability to escalate their own privileges. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. |
| Red Hat Bugzilla | 2022-01-08 05:30:25 UTC | CC | jokerman | |
| Red Hat Bugzilla | 2022-05-14 08:03:18 UTC | CC | marobrie | |
| Red Hat Bugzilla | 2022-12-01 05:23:58 UTC | CC | jesusr | |
| Red Hat Bugzilla | 2023-07-07 08:31:23 UTC | Assignee | security-response-team | nobody |
Back to bug 1829674