Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
phongnguyend/practical.cleanarchitecture
master @ 818f3b5
8
Fixes
0
CVEs
HIGH
Peak severity
37.5%
Coverage
Highlights
Auth Bypass: 5 prior fixes. Scrutinize any change in this area.
ClassifiedAds.Infrastructure/Web/Authorization/Policies/CustomAuthorizationPolicyProvider.cs: most-fixed (1 issue). Treat as high-risk during review.
4 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Auth Bypass: The application previously relied on loose, static string-based authorization policies rather than structured, permission-based checks, leaving endpoints vulnerable to policy bypasses during permission evaluations.
Auth Bypass: A null security stamp returned by GetSecurityStampAsync could compromise identity validation, allowing active sessions to persist even after password resets or account modifications. Returning an empty string prevents ASP.NET Core Identity validation failures from defaulting to an open state.
Auth Bypass: Sensitive backend microservice endpoints, such as UserService and AuditLogBase, lacked explicit authentication middleware and authorization attributes, exposing raw gRPC endpoints to internal or external network bypasses.