Security context

Highlights

Auth Bypass: 6 prior fixes. Scrutinize any change in this area.

api/src/endpoints/oauth.rs: most-fixed (2 issues). Treat as high-risk during review.

5 high-severity fixes in this history; regressions here are high-impact.

Recurring patterns

Auth Bypass: Weaknesses in token signature verification and incomplete claims validation (such as audience and issuer) in the JWT authentication middleware allowed bypass of route protections. Ensure all route protection mechanisms explicitly validate all claims rather than relying on permissive library defaults.

Auth Bypass: Insecure parameters and improper ownership isolation inside the OAuth workflow allowed clients to assert elevated engineering privileges or bypass tenancy limits. Developers must strictly avoid relying on client-supplied boolean flags to authorize access to system settings.

Information Disclosure: Sensitive credentials and raw secrets have been exposed in API payloads due to the absence of active filtering on connection response serialization. Future implementations must consistently employ dedicated sanitized models to prevent internal fields from leaking.