CVE-2024-45313
Published: 02 September 2024
Summary
CVE-2024-45313 is a medium-severity Improper Access Control (CWE-284) vulnerability in Overleaf Overleaf. Its CVSS base score is 5.4 (Medium).
Operationally, ranked in the top 43.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-41434
Vulnerability details
Overleaf is a web-based collaborative LaTeX editor. When installing Server Pro using the Overleaf Toolkit from before 2024-07-17 or legacy docker-compose.yml from before 2024-08-28, the configuration for LaTeX compiles was insecure by default, requiring the administrator to enable the security…
more
features via a configuration setting (`SIBLING_CONTAINERS_ENABLED` in Toolkit, `SANDBOXED_COMPILES` in legacy docker-compose/custom deployments). If these security features are not enabled then users have access to the `sharelatex` container resources (filesystem, network, environment variables) when running compiles, leading to multiple file access vulnerabilities, either directly or via symlinks created during compiles. The setting has now been changed to be secure by default for new installs in the Toolkit and legacy docker-compose deployment. The Overleaf Toolkit has been updated to set `SIBLING_CONTAINERS_ENABLED=true` by default for new installs. It is recommended that any existing installations using the previous default setting migrate to using sibling containers. Existing installations can set `SIBLING_CONTAINERS_ENABLED=true` in `config/overleaf.rc` as a mitigation. In legacy docker-compose/custom deployments `SANDBOXED_COMPILES=true` should be used.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Defines roles, responsibilities, and access rules for configuration management activities, making improper access to configuration resources harder to exploit.
Baseline includes documented access control settings that are reviewed and maintained, reducing the ability to exploit improper access control.
Restricting available functions and services reduces the attack surface and enforces proper access control boundaries.
Tailoring selects and adjusts the precise set of access-control baselines and compensating controls required for the system, directly reducing improper access control exposure.
Central management enforces consistent access-control policies across systems, reducing the likelihood of missing or inconsistent enforcement.
Scans identify improper access control implementations and missing protections on system resources.
Explicit training on access control mechanisms and their operation makes improper access control harder to introduce via misconfiguration.
Guidance on effective use of access control mechanisms and known configuration vulnerabilities makes improper access control harder to exploit.