{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-24837 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-24837 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-24837 is a medium-severity vulnerability in hedgedoc, published on 11 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-24837 and fix it if it is affected.\n\nWhat it is: CVE-2022-24837 is a medium-severity vulnerability in hedgedoc, published on 11 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-24837 in the wild and no public exploit code.\n\nAffected product: hedgedoc. 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-2022-24837/ (Markdown: https://insights.sbomify.com/CVE-2022-24837/index.md)","id":"CVE-2022-24837","markdown":"https://insights.sbomify.com/CVE-2022-24837/index.md","name":"CVE-2022-24837","record":{"aliases":["GHSA-q6vv-2q26-j7rx"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"HedgeDoc markdown editor","requires_auth":"none","summary":"Attackers can enumerate uploaded image filenames to leak private document contents in HedgeDoc, requiring an upgrade to fix.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hedgedoc","vendor":"hedgedoc"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"HedgeDoc is an open-source, web-based, self-hosted, collaborative markdown editor. Images uploaded with HedgeDoc version 1.9.1 and later have an enumerable filename after the upload, resulting in potential information leakage of uploaded documents. This is especially relevant for private notes and affects all upload backends, except Lutim and imgur. This issue is patched in version 1.9.3 by replacing the filename generation with UUIDv4. If you cannot upgrade to HedgeDoc 1.9.3, it is possible to block POST requests to `/uploadimage`, which will disable future uploads.","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":"Enumerable upload file names in hedgedoc","id":"CVE-2022-24837","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Command Injection in Appointment Emails for Nextcloud Calendar","id":"CVE-2022-24838"},"packages":[],"prev":{"headline":"Inefficient Regular Expression Complexity in Nokogiri","id":"CVE-2022-24836"},"products":["hedgedoc"],"published":"2022-04-11","related":[{"cvss_score":10,"headline":"PDF export allows arbitrary file reads","id":"CVE-2021-29475","kev_date_added":null,"published":"2021-04-26"},{"cvss_score":8.7,"headline":"Stored XSS in mermaid diagrams","id":"CVE-2020-26287","kev_date_added":null,"published":"2020-12-28"},{"cvss_score":8.1,"headline":"XSS vector in slide mode speaker-view","id":"CVE-2021-39175","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":8.1,"headline":"Improper Neutralization of Script-Related HTML Tags in Notes","id":"CVE-2021-29503","kev_date_added":null,"published":"2021-05-19"},{"cvss_score":7.5,"headline":"Arbitary file upload","id":"CVE-2020-26286","kev_date_added":null,"published":"2020-12-28"},{"cvss_score":7.4,"headline":"Stored XSS in slide mode","id":"CVE-2021-21259","kev_date_added":null,"published":"2021-01-22"},{"cvss_score":6.5,"headline":"MySQL \u0026 free URL mode allows to hide existing notes in hedgedoc","id":"CVE-2024-45308","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["hedgedoc"]},"summary":"Attackers can enumerate uploaded image filenames to leak private document contents in HedgeDoc, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2022-24837/"}