نسخههای متأثر
- نسخههای متأثر
- = 1.3.0-2773
- نسخهٔ اصلاحشده
- 1.3.1
بهرهبرداری
شرح آسیبپذیری
Summary
When secureEnabled=true, FUXA 1.3.0-2773 still allows guest and invalid-token requests to read project, alarms, and scheduler APIs.
Details
In secure mode, requests with no token or an explicitly invalid token were still able to access protected read endpoints.
Confirmed behavior:
guest
GET /api/projectreturned200 OKinvalid-token requests to
/api/projectalso returned successful responses containing project dataguest and invalid-token requests also returned
200 OKon:/api/alarms/api/scheduler
Relevant code paths identified during analysis:
server/api/jwt-helper.jsverifyToken()converts missing-token or invalid-token states into guest context instead of rejecting the request
server/api/projects/index.jsserver/api/alarms/index.jsserver/api/scheduler/index.js
These handlers accepted the guest context and returned sensitive data in secure mode.
PoC
Tested only against isolated local lab instances under the original tester's control. No production, customer, shared, or third-party systems were involved.
Reproduction:
Start FUXA
1.3.0-2773.Set
secureEnabled=true.Send unauthenticated requests to:
GET /api/projectGET /api/alarmsGET /api/scheduler?id=test
Observe
200 OKresponses.Send the same requests with an explicitly invalid
x-access-tokenvalue.Observe the same successful responses.
The exact HTTP requests and local PoC script used for confirmation can be provided upon request.
Impact
This is an authentication/authorization weakness in secure mode.
Impact includes:
project metadata disclosure
alarms disclosure
scheduler information disclosure
assistance in reconnaissance/follow-on attacks
Operators who believe secure mode protects these APIs are impacted.
پیوندها
گزارشدهندگان
- north-echo

