Muhammad FaqihApplication security · Penetration testing
Test case 15 / 19PASS

Broken Object Level Authorization - Workshop - Mechanic Report (Unauthenticated)

Lab environment — not a production system

Screenshots and raw traffic are not translated; text within them may be in another language.

crAPI/Evidence/[PASS] Broken Object Level Authorization - Workshop - Mechanic Report (Unauthenticated)

01 — Notes

Test notes

Vulnerability

[PASS] Broken Object Level Authorization - Workshop - Mechanic Report (Unauthenticated)

Description

Tested access to the mechanic_report endpoint without authentication.

Impact

No impact: the server requires authentication and rejects the request (401).

CWE

CWE-306: Missing Authentication for Critical Function (tested, not vulnerable on this path)

OWASP

API1:2023 - Broken Object Level Authorization (negative test - unauthenticated path)

Scenario

Normal: read a report with a token -> 200. Exploitation: remove the token -> 401. PASS (authentication control holds).

Endpoint

GET http://127.0.0.1:8888/workshop/api/mechanic/mechanic_report?report_id={id}

Affected feature

Mechanic Service Report (crapi-workshop)

Remediation

Keep the authentication requirement; add object ownership verification (see the related [FAIL] finding).

Proof of concept

1) (Screenshot 1) NORMAL: GET mechanic_report?report_id=1 with a token -> 200. 2) (Screenshot 2) EXPLOITATION: resend WITHOUT the Authorization header -> 401 (authentication control holds).
View source note (English)
Vulnerability: [PASS] Broken Object Level Authorization - Workshop - Mechanic Report (Unauthenticated)

Description:
Tested access to the mechanic_report endpoint without authentication.

Impact:
No impact: the server requires authentication and rejects the request (401).

CWE:
CWE-306: Missing Authentication for Critical Function (tested, not vulnerable on this path)

OWASP:
API1:2023 - Broken Object Level Authorization (negative test - unauthenticated path)

Scenario:
Normal: read a report with a token -> 200. Exploitation: remove the token -> 401. PASS (authentication control holds).

Endpoint:
GET http://127.0.0.1:8888/workshop/api/mechanic/mechanic_report?report_id={id}

Affected Feature:
Mechanic Service Report (crapi-workshop)

Remediation:
Keep the authentication requirement; add object ownership verification (see the related [FAIL] finding).

POC:
1) (Screenshot 1) NORMAL: GET mechanic_report?report_id=1 with a token -> 200.
2) (Screenshot 2) EXPLOITATION: resend WITHOUT the Authorization header -> 401 (authentication control holds).

02 — Screenshots

Screenshots (2)

01 / Normal: report with a token (authenticated)

Normal flow: reading the mechanic report with a valid token returns 200.

02 / Result: report access without a token rejected (PASS)

Result (PASS): access without a token returns 401. Authentication held in this test, but BOLA is still possible with another user's token; see [FAIL].

03 — Requests and responses

HTTP captures

Some credential values are masked in this public HTML view. This does not mean every sensitive value or linked file has been redacted.

CAPTURE 01 / 1Normal: report with a token (authenticated)
HTTP request
GET /workshop/api/mechanic/mechanic_report?report_id=1 HTTP/1.1
Host: 127.0.0.1:8888
Authorization: Bearer [REDACTED-LAB-TOKEN]
HTTP response
HTTP/1.1 200 OK
Server: openresty/1.27.1.2
Content-Type: application/json
Content-Length: 479

{
  "id": 1,
  "mechanic": {
    "id": 1,
    "mechanic_code": "TRAC_JHN",
    "user": {
      "email": "[REDACTED-EMAIL]",
      "number": ""
    }
  },
  "vehicle": {
    "id": 3,
    "vin": "0NKPZ09IHOP508673",
    "owner": {
      "email": "[REDACTED-EMAIL]",
      "number": "9876570001"
    }
  },
  "problem_details": "My car BMW - 5 Series is having issues.\nCan you give me a call on my mobile 9876570001,\nOr send me an email at [REDACTED-EMAIL]\nThanks,\nRobot.\n",
  "status": "pending",
  "created_on": "28 September, 2026, 14:28:07",
  "updated_on": null,
  "comments": []
}

Normal flow: reading the mechanic report with a valid token returns 200.

CAPTURE 02 / 2Result: report access without a token rejected (PASS)
HTTP request
GET /workshop/api/mechanic/mechanic_report?report_id=1 HTTP/1.1
Host: 127.0.0.1:8888
Accept: application/json

# HEADER Authorization SENGAJA DIHAPUS
HTTP response
HTTP/1.1 401 Unauthorized
Server: openresty/1.27.1.2
Content-Type: application/json
Content-Length: 33

{
  "message": "JWT Token required!"
}

Result (PASS): access without a token returns 401. Authentication held in this test, but BOLA is still possible with another user's token; see [FAIL].