Skip to content

Security: zis3c/USAS-Class-Timetable

Security

docs/SECURITY.md

Security Policy

Supported Versions

Currently, only the latest release of USAS Class Timetable is actively supported with security updates.

Version Supported
1.0.x ✅
< 1.0 ❌

Security Architecture

The browser sends USAS API requests through a Cloudflare Pages Function proxy. The function checks the endpoint and method allowlist and forwards requests to https://mobile.usas.edu.my. It does not write request bodies or student sessions to a project database. Cloudflare processes requests as the hosting and proxy provider. See the Privacy Notice for storage and service details.

  • Login anti-bot (ALTCHA): Login uses a self-hosted ALTCHA proof-of-work challenge (no third party, no cookies, works on iOS/Safari). The browser solves a PBKDF2 challenge served by /api/altcha; the Pages Function verifies it and a Durable Object rejects reused challenges before proxying. ALTCHA_HMAC_KEY and the ALTCHA_REPLAY_GUARD binding are required in production. The x-altcha header is stripped upstream. You can also add a Cloudflare Rate Limiting rule on POST /api/usas/student/login_student.php. The proxy additionally enforces an endpoint/method allowlist and request-size limit, and drops client-supplied network headers before forwarding; the in-browser login throttle is a convenience, not a security control.
  • Browser storage: The session is stored in sessionStorage; timetable cache and preferences use localStorage. Logout clears the session and timetable cache.
  • Content Security Policy: Response headers restrict content sources and framing. Inline scripts are disallowed (script-src has no 'unsafe-inline'). CSP reduces risk; it does not prevent every XSS or browser compromise.
  • Monitoring: Sentry is optional (VITE_SENTRY_DSN) and strips query strings from error events and breadcrumbs so shared timetable payloads are not sent to a third party.

Reporting a Vulnerability

If you discover a security vulnerability within USAS Class Timetable, report it privately to the USAS STEM Club through the contact details listed on the project's GitHub page. Do not include real student credentials or timetable data in the report. Response time depends on maintainer availability.

Please do not publicly disclose the issue until it has been addressed by the maintainers. We will work with you to ensure a timely resolution.

There aren't any published security advisories