{"answers":{"affected":"2 open source packages ship an affected version, including Rambox. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17625 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17625 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17625 is a critical cross-site scripting vulnerability in n/a, published on 16 Oct 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-17625 and fix it if it is affected.\n\nWhat it is: CVE-2019-17625 is a critical cross-site scripting vulnerability in n/a, published on 16 Oct 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-17625 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Rambox (npm): affected all versions up to 0.6.9; no fix listed\n- Rambox (npm): affected all versions up to 0.6.9; no fix listed\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-17625/ (Markdown: https://insights.sbomify.com/CVE-2019-17625/index.md)","id":"CVE-2019-17625","markdown":"https://insights.sbomify.com/CVE-2019-17625/index.md","name":"CVE-2019-17625","record":{"aliases":["GHSA-2gc6-2h2g-ph48"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Rambox desktop app","requires_auth":"low_privilege","summary":"Stored XSS in Rambox service name field allows attackers to execute arbitrary OS commands via crafted payloads.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rambox","vendor":"rambox"}],"cvss":{"score":9,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"There is a stored XSS in Rambox 0.6.9 that can lead to code execution. The XSS is in the name field while adding/editing a service. The problem occurs due to incorrect sanitization of the name field when being processed and stored. This allows a user to craft a payload for Node.js and Electron, such as an exec of OS commands within the onerror attribute of an IMG element.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2019-10-31","github_poc":1,"max_poc_stars":19,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-10-31T03:40:07Z","kind":"github_poc","ref":"https://github.com/Ekultek/CVE-2019-17625","stars":19,"title":"Working exploit code for CVE-2019-17625"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Rambox RCE Vulnerability","id":"CVE-2019-17625","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"XML Injection in ReportLab","id":"CVE-2019-17626"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.6.9"],"package":"Rambox","purl":null,"source":"GHSA-2gc6-2h2g-ph48"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.6.9"],"package":"Rambox","purl":"pkg:npm/Rambox","source":"GHSA-2gc6-2h2g-ph48"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-17624"},"products":["n/a"],"published":"2019-10-16","related":[],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Stored XSS in Rambox service name field allows attackers to execute arbitrary OS commands via crafted payloads.","url":"https://insights.sbomify.com/CVE-2019-17625/"}