diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-12-20 16:37:47 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-12-20 16:37:47 +0300 |
commit | aee0a117a889461ce8ced6fcf73207fe017f1d99 (patch) | |
tree | 891d9ef189227a8445d83f35c1b0fc99573f4380 /doc/security/webhooks.md | |
parent | 8d46af3258650d305f53b819eabf7ab18d22f59e (diff) |
Add latest changes from gitlab-org/gitlab@14-6-stable-eev14.6.0-rc42
Diffstat (limited to 'doc/security/webhooks.md')
-rw-r--r-- | doc/security/webhooks.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/security/webhooks.md b/doc/security/webhooks.md index 89dd4f8e5fc..47ef90cbe55 100644 --- a/doc/security/webhooks.md +++ b/doc/security/webhooks.md @@ -26,11 +26,11 @@ sent. Webhook requests are made by the GitLab server itself and use a single (optional) secret token per hook for authorization (instead of a user or -repository-specific token). As a result, these may have broader access than -intended to everything running on the server hosting the webhook (which -may include the GitLab server or API itself, e.g., `http://localhost:123`). +repository-specific token). As a result, these requests may have broader access than +intended, including access to everything running on the server hosting the webhook. This +may include the GitLab server or API itself (for example, `http://localhost:123`). Depending on the called webhook, this may also result in network access -to other servers within that webhook server's local network (e.g., +to other servers within that webhook server's local network (for example, `http://192.168.1.12:345`), even if these services are otherwise protected and inaccessible from the outside world. |