Description
Azkaban through 4.0.0 omits project permission checks in the ScheduleServlet fetchSchedule action, allowing authenticated users to read any project's schedule configuration. Attackers can supply arbitrary project and flow identifiers to retrieve sensitive schedule details including execution times, cron expressions, flow parameters, and notification email lists without proper authorization.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| azkaban | azkaban | ≤ 4.0.0 | — |
References
- GitHub Issue #3348 issue-tracking
- https://github.com/azkaban/azkaban product
- https://github.com/azkaban/azkaban/blob/4.0.0/azkaban-web-server/src/main/java/azkaban/webapp/servlet/ScheduleServlet.java#L237-L262 technical-description
- https://github.com/azkaban/azkaban/blob/4.0.0/azkaban-web-server/src/main/java/azkaban/webapp/servlet/ScheduleServlet.java#L403-L412 technical-description
- azkaban 4.0.0 Release Notes release-notes
- VulnCheck Advisory: Azkaban through 4.0.0 Authorization Bypass via ScheduleServlet third-party-advisory