{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-6702 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-6702 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-6702 is a medium-severity vulnerability in n/a, published on 17 Mar 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-6702 and fix it if it is affected.\n\nWhat it is: CVE-2019-6702 is a medium-severity vulnerability in n/a, published on 17 Mar 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-6702 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-6702/ (Markdown: https://insights.sbomify.com/CVE-2019-6702/index.md)","id":"CVE-2019-6702","markdown":"https://insights.sbomify.com/CVE-2019-6702/index.md","name":"CVE-2019-6702","record":{"aliases":["GHSA-wp8m-443x-323m"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MasterCard Qkr! iOS app","requires_auth":"none","summary":"The MasterCard Qkr! iOS app fails to validate SSL certificates, allowing attackers to intercept sensitive data via man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"qkr\\!_with_masterpass","vendor":"mastercard"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"The MasterCard Qkr! app before 5.0.8 for iOS has Missing SSL Certificate Validation. NOTE: this CVE only applies to obsolete versions from 2016 or earlier.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2019-6702","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Missing authorization in n/a","id":"CVE-2019-6703"},"packages":[],"prev":{"headline":"Information disclosure in Fortinet FortiSIEM","id":"CVE-2019-6700"},"products":["n/a"],"published":"2019-03-17","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-04","vendors":["n/a"]},"summary":"The MasterCard Qkr! iOS app fails to validate SSL certificates, allowing attackers to intercept sensitive data via man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2019-6702/"}