From d16493b2de11cd0ab5b1f2c0b9aa41e2681a9df7 Mon Sep 17 00:00:00 2001 From: Michal Guerquin Date: Thu, 2 Mar 2023 14:59:54 -0500 Subject: [PATCH] Add a missing word --- .../authz-and-authn-docker-access-authorization-plugin.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/linux-hardening/privilege-escalation/docker-breakout/authz-and-authn-docker-access-authorization-plugin.md b/linux-hardening/privilege-escalation/docker-breakout/authz-and-authn-docker-access-authorization-plugin.md index 4d8a64db6..b0673cd2c 100644 --- a/linux-hardening/privilege-escalation/docker-breakout/authz-and-authn-docker-access-authorization-plugin.md +++ b/linux-hardening/privilege-escalation/docker-breakout/authz-and-authn-docker-access-authorization-plugin.md @@ -122,7 +122,7 @@ Note also that if you can **mount `/etc`** or any other folder **containing conf ## Unchecked API Endpoint -The of the sysadmin configuring this plugin would be to control which actions and with which privileges each user can perform. Therefore, if the admin takes a **blacklist** approach with the endpoints and the attributes he might **forget some of them** that could allow an attacker to **escalate privileges.** +The responsibility of the sysadmin configuring this plugin would be to control which actions and with which privileges each user can perform. Therefore, if the admin takes a **blacklist** approach with the endpoints and the attributes he might **forget some of them** that could allow an attacker to **escalate privileges.** You can check the docker API in [https://docs.docker.com/engine/api/v1.40/#](https://docs.docker.com/engine/api/v1.40/#)