{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2019-16752 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16752 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16752 is a medium-severity server-side request forgery vulnerability in n/a, published on 4 Dec 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-16752 and fix it if it is affected.\n\nWhat it is: CVE-2019-16752 is a medium-severity server-side request forgery vulnerability in n/a, published on 4 Dec 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-16752 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2019-16752/ (Markdown: https://insights.sbomify.com/CVE-2019-16752/index.md)","id":"CVE-2019-16752","markdown":"https://insights.sbomify.com/CVE-2019-16752/index.md","name":"CVE-2019-16752","record":{"aliases":["GHSA-rpw6-pjfj-6x6g"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Cryptocurrency wallet","requires_auth":"none","summary":"Attackers can force cryptocurrency wallets to send HTTP requests to arbitrary locations, potentially leaking user IP addresses and privacy.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dash_core","vendor":"dash"},{"product":"decentralized_anonymous_payment_system","vendor":"officialdapscoin"},{"product":"private_instant_verified_transactions","vendor":"pivx"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"An issue was discovered in Decentralized Anonymous Payment System (DAPS) through 2019-08-26. It is possible to force wallets to send HTTP requests to arbitrary locations, both on the local network and on the internet. This is a serious threat to user privacy, since it can possibly leak their IP address and the fact that they are using the product. This also affects Dash Core through 0.14.0.3 and Private Instant Verified Transactions (PIVX) through 3.4.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Server-side request forgery in n/a","id":"CVE-2019-16752","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2019-16753"},"packages":[],"prev":{"headline":"Devise Token Auth vulnerable to Cross-site Scripting","id":"CVE-2019-16751"},"products":["n/a"],"published":"2019-12-04","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can force cryptocurrency wallets to send HTTP requests to arbitrary locations, potentially leaking user IP addresses and privacy.","url":"https://insights.sbomify.com/CVE-2019-16752/"}