Fix BOLA (Broken Object Level Authorization) in Rails

BOLA (OWASP API1) is the ultimate low-hanging fruit for attackers. It occurs when your API trusts the ID provided in the request without verifying the requester's ownership. In Rails, this is usually caused by lazy controller lookups that ignore the current user's session context, allowing anyone to enumerate and exfiltrate records by simply incrementing an integer or guessing a UUID.

The Vulnerable Pattern

class InvoicesController < ApplicationController
  # GET /invoices/:id
  def show
    # VULNERABLE: Direct lookup from the global model scope.
    # An attacker can change the ID in the URL to view any user's invoice.
    @invoice = Invoice.find(params[:id])
    render json: @invoice
  end
end

The Secure Implementation

The fix relies on 'Relationship-Based Access Control'. Instead of querying the top-level 'Invoice' class, we chain the query through the 'current_user' association. This ensures that the database-level query is constrained to records owned by the requester. If the ID exists but belongs to another user, ActiveRecord will return a 404 (RecordNotFound) instead of leaking data. For complex apps, use a gem like Pundit to enforce 'authorize @record' patterns, which centralizes this logic into Policy objects.

class InvoicesController < ApplicationController
  # GET /invoices/:id
  def show
    # SECURE: Scope the lookup to the authenticated user's own records.
    # This automatically appends 'WHERE user_id = ?' to the SQL query.
    @invoice = current_user.invoices.find_by!(id: params[:id])
    render json: @invoice
  rescue ActiveRecord::RecordNotFound
    render json: { error: 'Resource not found or unauthorized' }, status: :not_found
  end
end