[medium] oauth-patterns: OAuth flow without PKCE #39
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
medium Finding
Scanner: oauth-patterns
Severity: medium
Rule: oauth-missing-pkce
Description
Authorization code flow should use PKCE (code_challenge/code_verifier) for public clients.
Location
File:
src/infrastructure/auth.rs(line 207)Code
Remediation
Add PKCE support by generating a code_verifier, creating a code_challenge from it, and including both in the authorization request. The code_verifier should be stored securely and used when exchanging the authorization code for an access token.
Fingerprint:
29d02c2b928ed957c10752516acb9af3056476965583abcd4ab0f5427b1a8416Generated by compliance-scanner
Labels: severity:medium, scanner:oauth-patterns, compliance-scanner