{"answers":{"affected":"2 open source packages ship an affected version, including remarkable. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12041 in the wild and no public exploit code.","fix":"Upgrade remarkable to 1.7.2 or later.","what":"CVE-2019-12041 is a high-severity denial of service vulnerability in n/a, published on 13 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-12041 and fix it if it is affected.\n\nWhat it is: CVE-2019-12041 is a high-severity denial of service vulnerability in n/a, published on 13 May 2019. 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-2019-12041 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- remarkable (npm): affected all versions; fixed in 1.7.2\n- remarkable (npm): affected all versions; fixed in 1.7.2\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-2019-12041/ (Markdown: https://insights.sbomify.com/CVE-2019-12041/index.md)","id":"CVE-2019-12041","markdown":"https://insights.sbomify.com/CVE-2019-12041/index.md","name":"CVE-2019-12041","record":{"aliases":["GHSA-q22g-8fr4-qpj4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript Markdown library","requires_auth":"none","summary":"Attackers can cause a denial of service in the remarkable JavaScript library by submitting a crafted CDATA section that triggers excessive regular expression processing.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"remarkable","vendor":"remarkable_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-1333","name":"Inefficient Regular Expression Complexity"}],"description":"lib/common/html_re.js in remarkable 1.7.1 allows Regular Expression Denial of Service (ReDoS) via a CDATA section.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Regular Expression Denial of Service in remarkable","id":"CVE-2019-12041","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2019-12042"},"packages":[{"ecosystem":"npm","fixed":["1.7.2"],"introduced":["0"],"last_affected":[],"package":"remarkable","purl":null,"source":"GHSA-q22g-8fr4-qpj4"},{"ecosystem":"npm","fixed":["1.7.2"],"introduced":["0"],"last_affected":[],"package":"remarkable","purl":"pkg:npm/remarkable","source":"GHSA-q22g-8fr4-qpj4"}],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2019-12040"},"products":["n/a"],"published":"2019-05-13","related":[{"cvss_score":6.1,"headline":"Cross-site Scripting in remarkable","id":"CVE-2019-12043","kev_date_added":null,"published":"2019-05-13"},{"cvss_score":6.1,"headline":"XSS in Data URI in remarkable","id":"CVE-2017-16006","kev_date_added":null,"published":"2018-06-04"},{"cvss_score":6.1,"headline":"Content Injection in remarkable","id":"CVE-2014-10065","kev_date_added":null,"published":"2018-05-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can cause a denial of service in the remarkable JavaScript library by submitting a crafted CDATA section that triggers excessive regular expression processing.","url":"https://insights.sbomify.com/CVE-2019-12041/"}