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

Exposure of confidential secret or token Duffel API token

Description

The response body contains content that matches the pattern of a Duffel API token was detected. Duffel API Tokens can be either read-write or read-only depending on how they were created. A malicious actor with access to a read-write token can execute orders, book flights or hotels, or view or modify customer lists. A read-only token can view customer lists, list bookings and flight information. 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 token:

  • Open and sign in to https://app.duffel.com/
  • On the top of the page select the Developers dropdown list and then select “Developers”
  • On the left-hand menu select “Access tokens”
  • Select the access token that was detected
  • Note the type of token (“Read and Write” or “Read Only”)
  • In the “Danger Zone” select “Delete token”
  • Recreate a new token with the same settings as the detected token

For more information see their documentation: https://duffel.com/docs/guides/getting-started-with-the-dashboard#access-tokens

Details

IDAggregatedCWETypeRisk
798.34false798PassiveHigh