{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-45313 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-45313 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2024-45313 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2024-45313 in the wild and no public exploit code.\n\nAffected product: overleaf. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-45313/ (Markdown: https://insights.sbomify.com/CVE-2024-45313/index.md)","id":"CVE-2024-45313","markdown":"https://insights.sbomify.com/CVE-2024-45313/index.md","name":"CVE-2024-45313","record":{"aliases":["GHSA-m95q-g8qg-wgj4"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Overleaf Server Pro","requires_auth":"low_privilege","summary":"Insecure default settings in Overleaf Server Pro allow users to access container resources during LaTeX compilation, enabling file access and privilege escalation.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"overleaf","vendor":"overleaf"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"},{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Insecure default setting for Server Pro installed via Overleaf toolkit","id":"CVE-2024-45313","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Flask-AppBuilder login form allows browser to cache sensitive fields","id":"CVE-2024-45314"},"packages":[],"prev":{"headline":"Arbitrary language parameter can passed to `aspell` executable via spelling requests in overleaf","id":"CVE-2024-45312"},"products":["overleaf"],"published":"2024-09-02","related":[{"cvss_score":5.3,"headline":"Arbitrary language parameter can passed to `aspell` executable via spelling requests in overleaf","id":"CVE-2024-45312","kev_date_added":null,"published":"2024-09-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-03","vendors":["overleaf"]},"summary":"Insecure default settings in Overleaf Server Pro allow users to access container resources during LaTeX compilation, enabling file access and privilege escalation.","url":"https://insights.sbomify.com/CVE-2024-45313/"}