Flowintel data exposure in template repository file access
flowintel
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| flowintel flowintel |
| No fix yet |
Original description
Flowintel's template repository subsystem did not adequately constrain file access to the configured repository base directory. Two related weaknesses existed:
- Repository registration and editing accepted arbitrary local paths without verifying they resolved inside the configured REPOSITORY_BASE_PATH, allowing an authenticated user to point a repository at any readable directory on the host. - Manifest and template file lookups used normalized (non-canonical) path joins and a startswith-based guard that could be bypassed by symbolic links, permitting reads of files outside the intended repository.
An authenticated user with the ability to add or edit a template repository could therefore cause the application to read and return the contents of arbitrary files readable by the service account, including configuration files, credentials, or other sensitive data.
Affected: Flowintel versions prior to 4.1.0.