正式なドキュメントは英語版であり、この日本語訳はAI支援翻訳により作成された参考用のものです。日本語訳の一部の内容は人間によるレビューがまだ行われていないため、翻訳のタイミングにより英語版との間に差異が生じることがあります。最新かつ正確な情報については、英語版をご参照ください。

Exposure of confidential secret or token GitLab incoming email token

Description

The response body contains content that matches the pattern of a GitLab incoming email token was identified. Your incoming email token authenticates you when you create a new issue by email, and is included in your personal project-specific email addresses. It cannot be used to access any other data. A malicious actor with access to this token can create issues as if they were you. Exposing this value could allow attackers to gain access to all resources granted by this token.

Remediation

For general guidance on handling security incidents with regards to leaked keys, please see the GitLab documentation on Credential exposure to the internet.

To regenerate a feed token:

  • Sign in to your GitLab account and access the User settings left-hand side menu, select “Access tokens”
  • Under the “Incoming email token” section, select the “reset this token” link
  • When prompted select “OK”

For more information, please see GitLabs documentation on feed tokens.

Details

IDAggregatedCWETypeRisk
798.149false798PassiveHigh