{"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-12043 in the wild and no public exploit code.","fix":"Upgrade remarkable to 1.7.2 or later.","what":"CVE-2019-12043 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-12043 and fix it if it is affected.\n\nWhat it is: CVE-2019-12043 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-12043 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-12043/ (Markdown: https://insights.sbomify.com/CVE-2019-12043/index.md)","id":"CVE-2019-12043","markdown":"https://insights.sbomify.com/CVE-2019-12043/index.md","name":"CVE-2019-12043","record":{"aliases":["GHSA-36m4-6v6m-4vpr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Markdown parser library","requires_auth":"none","summary":"Attackers can execute arbitrary JavaScript via unprintable characters in URLs due to improper filtering in the remarkable markdown parser.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"remarkable","vendor":"remarkable_project"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"In remarkable 1.7.1, lib/parser_inline.js mishandles URL filtering, which allows attackers to trigger XSS via unprintable characters, as demonstrated by a \\x0ejavascript: URL.","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":"Cross-site Scripting in remarkable","id":"CVE-2019-12043","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-12044"},"packages":[{"ecosystem":"npm","fixed":["1.7.2"],"introduced":["0"],"last_affected":[],"package":"remarkable","purl":null,"source":"GHSA-36m4-6v6m-4vpr"},{"ecosystem":"npm","fixed":["1.7.2"],"introduced":["0"],"last_affected":[],"package":"remarkable","purl":"pkg:npm/remarkable","source":"GHSA-36m4-6v6m-4vpr"}],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2019-12042"},"products":["n/a"],"published":"2019-05-13","related":[{"cvss_score":7.5,"headline":"Regular Expression Denial of Service in remarkable","id":"CVE-2019-12041","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 execute arbitrary JavaScript via unprintable characters in URLs due to improper filtering in the remarkable markdown parser.","url":"https://insights.sbomify.com/CVE-2019-12043/"}