{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55630 exists.","fix":"No fix has been published for CVE-2024-55630 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-55630 is a low-severity denial of service vulnerability in laurent22 joplin, published on 7 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-55630 and fix it if it is affected.\n\nWhat it is: CVE-2024-55630 is a low-severity denial of service vulnerability in laurent22 joplin, published on 7 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55630 exists.\n\nAffected product: laurent22 joplin. 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-55630/ (Markdown: https://insights.sbomify.com/CVE-2024-55630/index.md)","id":"CVE-2024-55630","markdown":"https://insights.sbomify.com/CVE-2024-55630/index.md","name":"CVE-2024-55630","record":{"aliases":["GHSA-5cch-jr52-qffh"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Joplin note taking app","requires_auth":"none","summary":"An attacker can cause a temporary denial of service in the Joplin note viewer by exploiting DOM clobbering via the name attribute.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"joplin","vendor":"joplin_project"}],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Joplin is a free, open source note taking and to-do application, which can handle a large number of notes organised into notebooks. Joplin's HTML sanitizer allows the `name` attribute to be specified. If `name` is set to the same value as an existing `document` property (e.g. `querySelector`), that property is replaced with the element. This vulnerability's only known impact is denial of service. The note viewer fails to refresh until closed and re-opened with a different note. This issue has been addressed in version 3.2.8 and all users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"DOM Clobbering leads to temporary DOS in the note viewer in Joplin","id":"CVE-2024-55630","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in Trend Micro Apex One","id":"CVE-2024-55631"},"packages":[],"prev":{"headline":"Suricata generic detection bypass using TCP urgent support","id":"CVE-2024-55629"},"products":["joplin"],"published":"2025-02-07","related":[{"cvss_score":9.8,"headline":"Joplin Vulnerable to Code Injection","id":"CVE-2022-23340","kev_date_added":null,"published":"2022-02-08"},{"cvss_score":9.7,"headline":"Joplin has a parsing error leading to Cross-site Scripting (XSS)","id":"CVE-2024-40643","kev_date_added":null,"published":"2024-09-09"},{"cvss_score":8.9,"headline":"Arbitrary code execution on click of PDF links in Joplin","id":"CVE-2023-45673","kev_date_added":null,"published":"2024-06-21"},{"cvss_score":8.8,"headline":"Privilege escalation in Joplin server via user patch endpoint","id":"CVE-2025-27134","kev_date_added":null,"published":"2025-04-30"},{"cvss_score":8.2,"headline":"Safe mode Cross-site Scripting (XSS) vulnerability in Joplin","id":"CVE-2023-37898","kev_date_added":null,"published":"2024-06-21"},{"cvss_score":8.2,"headline":"Cross-site Scripting (XSS) when pasting HTML into the rich text editor in Joplin","id":"CVE-2023-38506","kev_date_added":null,"published":"2024-06-21"},{"cvss_score":8.2,"headline":"Cross site scripting (XSS) when clicking on an untrusted `\u003cmap\u003e` link in Joplin","id":"CVE-2023-39517","kev_date_added":null,"published":"2024-06-21"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-10","vendors":["laurent22"]},"summary":"An attacker can cause a temporary denial of service in the Joplin note viewer by exploiting DOM clobbering via the name attribute.","url":"https://insights.sbomify.com/CVE-2024-55630/"}