Grafana detector: unexpected HTTP response status 404

[rgmz]

Reproducer

Found unverified result 🐷🔑❓
Verification issue: unexpected HTTP response status 404
Detector Type: Grafana
Decoder Type: PLAIN
Raw result: glc_eyJvIjoiMjA0NjMwIiwibiI6InRlc3QtdG9rZW4iLCJrIjoiWHc5MTVXOWtNOWxsNHcyZHEyIiwibSI6eyJyIjoicHJvZC0wIn19
Commit: 62e5c36c60ace8340db72ff3ca109c81be91cadd
File: fuzz/corpus/0f6e27df5b57eb198b8068f312bc80815b06488d
Line: 1
Link: https://github.com/Samsung/CredSweeper/blob/62e5c36c60ace8340db72ff3ca109c81be91cadd/fuzz/corpus/0f6e27df5b57eb198b8068f312bc80815b06488d#L1
Repository: https://github.com/Samsung/CredSweeper.git
Timestamp: 2023-07-25 13:06:10 +0000

Body:

{
  "code": "NotFound",
  "message": "stack region not found",
  "requestId": "96298543-a1a8-4e81-a806-84bf1848d492"
}

https://grafana.com/docs/grafana-cloud/developer-resources/api-reference/cloud-api/#list-a-set-of-tokens

[kashifkhan0771]

@ankushgoel27 This issue is related to the Grafana detector, which does not use any domain pattern. The domain pattern is part of a separate detector, GrafanaServiceAccount.

[kashifkhan0771]

As per our code, we are using a fixed region ?region=us. I tested the API with this region as well as other regions, and it worked fine. The only time I was able to reproduce the error was when I provided an invalid region in the API request.

[kashifkhan0771]

@rgmz I was only able to reproduce this error when using an invalid region, but our detector uses a fixed, valid region. Could you share more details about the error and how you encountered it?

[rgmz]

@rgmz I was only able to reproduce this error when using an invalid region, but our detector uses a fixed, valid region. Could you share more details about the error and how you encountered it?

The token itself contains region information (m.r):

$ base64 -d <<< "eyJvIjoiMjA0NjMwIiwibiI6InRlc3QtdG9rZW4iLCJrIjoiWHc5MTVXOWtNOWxsNHcyZHEyIiwibSI6eyJyIjoicHJvZC0wIn19"
{"o":"204630","n":"test-token","k":"Xw915W9kM9ll4w2dq2","m":{"r":"prod-0"}}

The original reproducer no longer exhibits the behaviour. Not sure if they've changed their API behaviour.

[kashifkhan0771]

The original reproducer no longer exhibits the behaviour. Not sure if they've changed their API behaviour.

Can we close this issue in that case?

[rgmz]

I haven't used TruffleHog in the past few months. It would checking if this error has been seen recently — does Forager record errors?