{"answers":{"affected":"2 open source packages ship an affected version, including vega-util. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10806 in the wild and no public exploit code.","fix":"Upgrade vega-util to 1.13.1 or later.","what":"CVE-2019-10806 is a medium-severity code injection vulnerability in vega-util, published on 9 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10806 and fix it if it is affected.\n\nWhat it is: CVE-2019-10806 is a medium-severity code injection vulnerability in vega-util, published on 9 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10806 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vega-util (npm): affected all versions; fixed in 1.13.1\n- vega-util (npm): affected all versions; fixed in 1.13.1\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-10806/ (Markdown: https://insights.sbomify.com/CVE-2019-10806/index.md)","id":"CVE-2019-10806","markdown":"https://insights.sbomify.com/CVE-2019-10806/index.md","name":"CVE-2019-10806","record":{"aliases":["GHSA-6hwh-rqwf-cxxr","SNYK-JS-VEGAUTIL-559223"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript utility library","requires_auth":"low_privilege","summary":"Attackers can manipulate the Object prototype via vega.mergeConfig, potentially leading to arbitrary code execution in applications using this JavaScript library.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"vega","vendor":"vega_project"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"vega-util prior to 1.13.1 allows manipulation of object prototype. The 'vega.mergeConfig' method within vega-util could be tricked into adding or modifying properties of the Object.prototype.","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":"Improperly Controlled Modification of Dynamically-Determined Object Attributes in vega-util","id":"CVE-2019-10806","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Improper Neutralization of Special Elements used in an OS Command in Blamer","id":"CVE-2019-10807"},"packages":[{"ecosystem":"npm","fixed":["1.13.1"],"introduced":["0"],"last_affected":[],"package":"vega-util","purl":null,"source":"GHSA-6hwh-rqwf-cxxr"},{"ecosystem":"npm","fixed":["1.13.1"],"introduced":["0"],"last_affected":[],"package":"vega-util","purl":"pkg:npm/vega-util","source":"GHSA-6hwh-rqwf-cxxr"}],"prev":{"headline":"Exposure of Resource to Wrong Sphere in valib","id":"CVE-2019-10805"},"products":["vega-util"],"published":"2020-03-09","related":[{"cvss_score":8.7,"headline":"XSS in Vega","id":"CVE-2020-26296","kev_date_added":null,"published":"2020-12-30"},{"cvss_score":8.1,"headline":"Vega XSS via expression abusing vlSelectionTuples function array map calls in environments with satisfactory function gadgets in the global scope","id":"CVE-2025-65110","kev_date_added":null,"published":"2026-01-05"}],"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 manipulate the Object prototype via vega.mergeConfig, potentially leading to arbitrary code execution in applications using this JavaScript library.","url":"https://insights.sbomify.com/CVE-2019-10806/"}