CyberRota Analysis
AI-GeneratedThe vulnerability arises from the report.get procedure, which allows authenticated users to retrieve sensitive report configurations using only a reportId, bypassing necessary access controls tied to projectId or organizationId. This oversight could lead to unauthorized access to detailed report information, including project associations and configurations. Organizations utilizing this affected procedure should prioritize remediation to prevent potential data exposure and ensure proper access controls are enforced.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
The report.get procedure in packages/trpc/src/routers/report.ts accepted only a reportId and returned getReportById(reportId) directly. The enforceAccess middleware in packages/trpc/src/trpc.ts evaluates membership only when the input carries a projectId or organizationId key, so an input consisting of a reportId alone passed through unchecked, and getReportById in packages/db/src/services/reports.service.ts performs a findUnique on the report id with no project scoping. Any authenticated user could therefore read the full configuration of any saved report on the instance, including the owning projectId, event series, filters, breakdowns and formulas, by supplying its identifier. The adjacent update, delete and duplicate procedures resolve the report first and check getProjectAccess against the report's own projectId, so the omission was specific to this procedure.