Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with correct endpoint & pattern detection in AeroWorkFlow #3434

Open
sahil9001 opened this issue Oct 16, 2024 · 0 comments · May be fixed by #3435
Open

Issue with correct endpoint & pattern detection in AeroWorkFlow #3434

sahil9001 opened this issue Oct 16, 2024 · 0 comments · May be fixed by #3435
Labels

Comments

@sahil9001
Copy link
Contributor

sahil9001 commented Oct 16, 2024

Please review the Community Note before submitting

TruffleHog Version

Trace Output

Verification Endpoint

Expected Behavior

Correct API endpoint for verification must be used /api/{accountid}/me which aligns with other detector patterns as well.

Reference: https://api.aeroworkflow.com/swagger/index.html

Actual Behavior

Currently the API for endpoint verification is /api/{accountid}/v1/AeroAppointments. This endpoint is not appropriate as it might involve COGs.

Pattern Detection

Expected Behavior

The current API key pattern should match the pattern required.

Actual Behavior

The \b at the end of the regex is looking for a word boundary. In this case, the 20-character sequence is immediately followed by a /, which is not a word character. The word boundary \b is expecting a transition from a word character to a non-word character or the end of the string, which doesn't occur here.

Steps to Reproduce

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Environment

  • OS: [e.g. iOS]
  • Version [e.g. 22]

Additional Context

References

  • #0000
@sahil9001 sahil9001 added the bug label Oct 16, 2024
@sahil9001 sahil9001 changed the title Issue with correct endpoint in AeroWorkFlow Issue with correct endpoint & pattern detection in AeroWorkFlow Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging a pull request may close this issue.

1 participant