CVE-2024-45313 Insecure default setting for Server Pro installed via Overleaf toolkit

Medium 5.4 Published Updated

Insecure default settings in Overleaf Server Pro allow users to access container resources during LaTeX compilation, enabling file access and privilege escalation.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2024-45313?

CVE-2024-45313 is a medium-severity vulnerability in overleaf, published on 2 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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 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.

Weakness: CWE-284, CWE-1188

Which versions are affected by CVE-2024-45313?

It affects 1 product.

Products include Overleaf Overleaf.

How do I fix CVE-2024-45313?

No fix has been published for CVE-2024-45313 yet. Limit exposure of the affected software until one is available.

Is CVE-2024-45313 being exploited?

There is no known exploitation of CVE-2024-45313 in the wild and no public exploit code.

Sources

Also known as GHSA-m95q-g8qg-wgj4.

Is CVE-2024-45313 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free